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

Map Reduce with sharded output collection creates orphan documents

    XMLWordPrintableJSON

Details

    • Bug
    • Status: Closed
    • Major - P3
    • Resolution: Gone away
    • None
    • None
    • MapReduce, Sharding
    • ALL
    • Sharding 2019-01-28, Sharding 2019-02-11

    Description

      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.

      Attachments

        Issue Links

          Activity

            People

              randolph@mongodb.com Randolph Tan
              jon.rangel@mongodb.com Jon Rangel (Inactive)
              Votes:
              1 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: