Playbook and internal commands to resolve DB metadata inconsistency

XMLWordPrintableJSON

    • Type: Improvement
    • Resolution: Done
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • None
    • Catalog and Routing
    • CAR Team 2025-04-14
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      Following from SPM-3729, shards will authoritatively own the DB metadata. We have also updated the check metadata consistency command to check for any inconsistency between various metadata stores (config server and shards) and the relevant caches.

      What if we find an inconsistency or need a way to manipulate the metadata for maintenance?

      This ticket will brainstorm the scenarios we might encounter, code any needed changes to the server, and write a maintenance playbook.

      [Note: Also consider the future projects that will make the collection metadata authoritative as well.]

            Assignee:
            Sulabh Mahajan
            Reporter:
            Sulabh Mahajan
            Votes:
            0 Vote for this issue
            Watchers:
            8 Start watching this issue

              Created:
              Updated:
              Resolved: