Shard may not realize that collection is already sharded after restart

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Duplicate
    • Priority: Major - P3
    • None
    • Affects Version/s: 2.6.4, 3.0.9, 3.3.9, 3.4.2, 3.5.4
    • Component/s: Sharding
    • Sharding
    • ALL
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      Until a mongos who knows that the collection is sharded informs the shard. The issue is that shards assume that collections are unsharded by default and it should double check with the config servers if this is the first time it sees a namespace and mongos sends a version of (0, 0|0).

        1. zero_version.js
          1 kB

              Assignee:
              [DO NOT USE] Backlog - Sharding Team
              Reporter:
              Randolph Tan
              Votes:
              0 Vote for this issue
              Watchers:
              14 Start watching this issue

                Created:
                Updated:
                Resolved: