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

mapReduce output to sharded collection leaves orphans and then uses them in subsequent map/reduce

    XMLWordPrintableJSON

Details

    • Icon: Bug Bug
    • Resolution: Duplicate
    • Icon: Major - P3 Major - P3
    • None
    • 2.4.8, 2.6.4
    • MapReduce, Sharding
    • None
    • ALL

    Description

      When you finish any sharded:true output run of MapReduce, it leaves orphans in the shards from the end of first pass and then those influence subsequent runs.

      Attachments

        Activity

          People

            greg_10gen Greg Studer
            asya.kamsky@mongodb.com Asya Kamsky
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: