Updating config.shards can lose information

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Gone away
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • Sharding EMEA
    • ALL
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      The ShardingReplicaSetChangeListener writes to config.shards from multiple nodes without synchronization or version information: https://github.com/mongodb/mongo/blob/c6c9c62b8abe5ca36ec65320c813eaf81735f02a/src/mongo/s/mongos_main.cpp#L547. This can result in newer updates being replaced by older information.

            Assignee:
            [DO NOT USE] Backlog - Sharding EMEA
            Reporter:
            Lamont Nelson
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

              Created:
              Updated:
              Resolved: