Sharding an empty collection in mixed-shard version configurations may leave all chunks on the primary shard

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Fixed
    • Priority: Major - P3
    • 4.0.6, 4.1.8
    • Affects Version/s: 4.0.5
    • Component/s: Sharding
    • None
    • Fully Compatible
    • ALL
    • v4.0
    • Sharding 2019-02-11
    • 50
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None

      In partially upgraded clusters, whose config server is at version 4.0.5 and shards are at pre-4.0.3 (includes 3.6), sharding an empty collection with hashed sharding or performing map/reduce with outputting to an empty collection (with any kind of sharding) will end up placing all chunks on the primary shard of the collection.

      This is not a correctness issue, but it means that the balancer will have to move non-empty chunks later on and thus defeats the purpose of pre-sharding the collection.

            Assignee:
            Kaloian Manassiev
            Reporter:
            Kaloian Manassiev
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: