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

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Duplicate
    • Priority: Major - P3
    • None
    • Affects Version/s: 2.4.8, 2.6.4
    • Component/s: MapReduce, Sharding
    • None
    • ALL
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None

      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.

            Assignee:
            Greg Studer (Inactive)
            Reporter:
            Asya Kamsky
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

              Created:
              Updated:
              Resolved: