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

newly sharded collection requires config info reload on the mongod

    XMLWordPrintable

Details

    • Bug
    • Status: Closed
    • Major - P3
    • Resolution: Fixed
    • 2.1.0
    • 2.0.5, 2.1.0
    • Sharding
    • None
    • 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

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

              Dates

                Created:
                Updated:
                Resolved: