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

Handle all failed shardCollection commands well

XMLWordPrintableJSON

    • Type: Icon: Bug Bug
    • Resolution: Done
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: None
    • Component/s: Sharding
    • None
    • Sharding EMEA
    • ALL

      Two parts - make subsequent shardCollections possible without flushing configuration, and handle failed splitVector command by creating default Min->Max chunk and printing a warning of some kind.

      Additionally, if there are network troubles it is possible for a shardCollection command to fail halfway through, in a state where the collection is not fully sharded, but extra chunk entries have been created that prevent another shardCollection call from working. In this case, a rollback to the unsharded state should be attempted, both by the initial failed shardCollection command, as well as by the subsequent shardCollection command if necessary (for instance, if network issues persist that prevent the first command's rollback from working).

            Assignee:
            backlog-server-sharding-emea [DO NOT USE] Backlog - Sharding EMEA
            Reporter:
            greg_10gen Greg Studer
            Votes:
            6 Vote for this issue
            Watchers:
            10 Start watching this issue

              Created:
              Updated:
              Resolved: