Uploaded image for project: 'Core Server'
  1. Core Server
  2. SERVER-103815

Add a JS test to confirm the playbook to fix metadata inconsistency is correct

    • Type: Icon: Task Task
    • Resolution: Unresolved
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • Catalog and Routing
    • 2
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      SPM-3729 changed how database metadata is maintained across the cluster. There are three copies that stay in-sync, on CSRS, on shards and in-memory DSS.

      We wrote a playbook to fix the inconsistency if it were to ever happen. We should write a JS test to create that scenario of inconsistency and make sure the procedure we suggest is in fact tested.

            Assignee:
            Unassigned Unassigned
            Reporter:
            sulabh.mahajan@mongodb.com Sulabh Mahajan
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated: