Map Reduce with sharded output collection creates orphan documents

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Done
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: MapReduce, Sharding
    • ALL
    • Sharding 2019-01-28, Sharding 2019-02-11
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      During the post-processing phase of a map reduce run, when a shard pulls the documents for the chunks (of the output collection) that it owns from other shard(s), those documents are not deleted from the source shard(s). This may result in a large number of orphan documents which greatly increases the storage size of the output collection.

      When documents are migrated across shards during post-processing, they should be removed from the source shard.

              Assignee:
              Randolph Tan
              Reporter:
              Jon Rangel (Inactive)
              Votes:
              1 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: