Concurrent mapReduce replace with setFCV between 3.4 and 3.6 can cause errors with UUID assignment/removal

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Won't Fix
    • Priority: Major - P3
    • None
    • Affects Version/s: 3.6.6
    • Storage Execution
    • ALL
    • 54
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      Running a concurrency workload with setFCV toggling between 3.4 and 3.6 and mapReduce replace may cause collection validation to fail the UUID checks.

              Assignee:
              [DO NOT USE] Backlog - Storage Execution Team
              Reporter:
              Maria van Keulen
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

                Created:
                Updated:
                Resolved: