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

Add writeConcern as a field in config.migrations

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

      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:
            backlog-server-sharding [DO NOT USE] Backlog - Sharding Team
            Reporter:
            janna.golden@mongodb.com Janna Golden
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: