checkMetadataConsistency command may skip a database when a concurrent movePrimary happens

XMLWordPrintableJSON

    • Type: Improvement
    • Resolution: Won't Do
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • None
    • Catalog and Routing
    • None
    • 3
    • 🟥 DDL
    • None
    • None
    • None
    • None
    • None
    • None

      The checkMetadataConsistency command may skip a database if:

      • the checkMetadataConsistency command is executed at the cluster level
      • and there is a concurrent movePrimary operation ongoing

        1. repro.js
          1 kB
          Silvia Surroca
        2. repro.patch
          2 kB
          Silvia Surroca

              Assignee:
              Unassigned
              Reporter:
              Silvia Surroca
              Votes:
              0 Vote for this issue
              Watchers:
              8 Start watching this issue

                Created:
                Updated:
                Resolved: