newly sharded collection requires config info reload on the mongod

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Done
    • Priority: Major - P3
    • 2.0.5, 2.1.0
    • Affects Version/s: 2.1.0
    • Component/s: Sharding
    • None
    • ALL
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None

      If we shard a collection with one mongos, the mongod will not know about the change until a setShardVersion command comes in. Since other mongoses do not know about the change, they may never send another setShardVersion command if they don't re-establish connections.

      This can cause mongoses not to split, if the shard command comes from one mongos which then is not used to insert the data.

            Assignee:
            Greg Studer (Inactive)
            Reporter:
            Greg Studer (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: