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

Drop the collection after removing the partially written chunks for mapReduce in mongos_manual_intervention_actions.js

    • Type: Icon: Bug Bug
    • Resolution: Fixed
    • Priority: Icon: Major - P3 Major - P3
    • 3.6.9, 4.0.2, 4.1.1
    • Affects Version/s: None
    • Component/s: Sharding
    • None
    • Fully Compatible
    • ALL
    • v4.0, v3.6
    • 35

      As of SERVER-33538, we no longer allow mapReduce to be called with an existing unsharded output collection. If the shardCollection command fails (due to a stepdown, etc.) on the first attempt of mapReduce, the collection will be created but not sharded so we will fail the command entirely. We should drop the collection in addition to cleaning up the partially written chunks in the case of shardCollection failing during mapReduce.

            Assignee:
            cheahuychou.mao@mongodb.com Cheahuychou Mao
            Reporter:
            janna.golden@mongodb.com Janna Golden
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: