Confirm write to config.shards does not create an oplog entry

XMLWordPrintableJSON

    • Type: Task
    • Resolution: Works as Designed
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • None
    • Replication
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      As discussed here, we want to check that no oplog entry is created for the insert in config.shards.

      Not doing this in SERVER-82913 itself since there are some changes to be done to allow writes on the config database. Right now it fails with "Not primary while performing update on config.databases".

              Assignee:
              [DO NOT USE] Backlog - Replication Team
              Reporter:
              Frederic Vitzikam (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

                Created:
                Updated:
                Resolved: