Wrong number of documents reported deleted when using batched deletes in 6.0

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Fixed
    • Priority: Major - P3
    • 6.0.16
    • Affects Version/s: 6.0.16
    • Component/s: None
    • Query Execution
    • Fully Compatible
    • ALL
    • Hide

      Execute jstests/sharding/swallow_unnecessary_uuid_mismatch_error.js with the sharding_batched_deletes_passthrough suite

      Show
      Execute jstests/sharding/swallow_unnecessary_uuid_mismatch_error.js with the sharding_batched_deletes_passthrough suite
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      With the backport to 6.0 of SERVER-79049 we had to disable the jstests/sharding/swallow_unnecessary_uuid_mismatch_error.js test in the sharding_batched_deletes_passthrough suite.

      This is because instead of returning the expected number of documents deleted to be 3 it instead returns 4.

      Note that it doesn't actually affect the end result. A simple scan of the collection afterwards returns the full collection only containing 3 documents less. This is instead a problem of misleading results. It's also not happening on 7.0+.

              Assignee:
              Zixuan Zhuang
              Reporter:
              Jordi Olivares Provencio
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

                Created:
                Updated:
                Resolved: