shardCollection should warn if numInitialChunks is used with non-hashed sharded key

XMLWordPrintableJSON

    • Type: Improvement
    • Resolution: Done
    • Priority: Minor - P4
    • 3.3.6
    • Affects Version/s: None
    • Component/s: Sharding
    • None
    • Minor Change
    • Sharding 12 (04/01/16), Sharding 13 (04/22/16), Sharding 14 (05/13/16)
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None

      Currently if a user shards a collection and includes numInitialChunks without a hashed shard key, everything will succeed but the initial chunks value will be ignored. The user in this case could be rightly confused as to what has happened, and reviewing the logs will only indicate that "numChunks : 1".

      Suggest a warning be given that numInitialChunks is being ignored in these cases

            Assignee:
            Misha Tyulenev (Inactive)
            Reporter:
            Andre de Frere
            Votes:
            1 Vote for this issue
            Watchers:
            9 Start watching this issue

              Created:
              Updated:
              Resolved: