Add writeConcern as a field in config.migrations

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Won't Fix
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: Sharding
    • Sharding
    • ALL
    • 20
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      If a config server steps down and a new primary recovers migrations from config.migrations, it will not know what write concern the initial request was sent with and can lead to reads on secondaries being incorrect.

              Assignee:
              [DO NOT USE] Backlog - Sharding Team
              Reporter:
              Janna Golden
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: