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

newly sharded collection requires config info reload on the mongod

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major - P3
    • Resolution: Fixed
    • Affects Version/s: 2.1.0
    • Fix Version/s: 2.0.5, 2.1.0
    • Component/s: Sharding
    • Labels:
      None
    • Operating System:
      ALL

      Description

      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.

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              greg_10gen Greg Studer
              Reporter:
              greg_10gen Greg Studer
              Participants:
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved: