The range deleter should retry on write conflict exceptions

XMLWordPrintableJSON

    • Fully Compatible
    • ALL
    • v4.2
    • Sharding 2019-02-25, Sharding 2019-06-03, Sharding 2019-06-17
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      The range deleter deletes orphan documents by constructing a PlanExecutor with a YIELD_MANUAL yield policy. Because of this, any write conflict errors encountered will be re-thrown, but there is no WriteConflictRetry loop in CollectionRangeDeleter::cleanUpNextRange, causing post-migration orphan cleanup and cleanupOrphaned commands to fail unnecessarily.

      The net effect of this is that more orphans remain on the system.

              Assignee:
              Alexander Taskov (Inactive)
              Reporter:
              Jack Mulrow
              Votes:
              0 Vote for this issue
              Watchers:
              7 Start watching this issue

                Created:
                Updated:
                Resolved: