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

Shard should directly update config.shards on successful reconfig

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

      The update is currently made from Mongos in updateReplicaSetOnConfigServer(). This is just best effort.

      This probably has to be done from _doReplSetReconfig however it requires some effort. I see that the reconfig is still supported when the node is not a writable primary and in the case of catalog shard won't be able to do a replicated write. If we remove this logic from Mongos and have cases when it fails in mongod, it may become even worse. Perhaps kaloian.manassiev@mongodb.com has some ideas?

            backlog-server-sharding-nyc [DO NOT USE] Backlog - Sharding NYC
            andrew.shuvalov@mongodb.com Andrew Shuvalov (Inactive)
            0 Vote for this issue
            4 Start watching this issue