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

Handle stale config after promotion from replSet to a shard

XMLWordPrintableJSON

    • Type: Icon: Bug Bug
    • Resolution: Duplicate
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • None
    • Cluster Scalability
    • ALL

      The node will start performing shard version checks once sharding is enabled. We need to make sure that existing connections that go straight to the shard would still be able to continue on performing crud ops

            Assignee:
            Unassigned Unassigned
            Reporter:
            randolph@mongodb.com Randolph Tan
            Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

              Created:
              Updated:
              Resolved: