MigrationChunkClonerSourceLegacy::nextCloneBatch should ignore prepare conflict

XMLWordPrintableJSON

    • Type: Task
    • Resolution: Unresolved
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • Cluster Scalability
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      MigrationChunkClonerSourceLegacy::nextCloneBatch should ignore prepare conflict when fetching documents.

      Otherwise, they will end up unnecessarily waiting for prepare conflict to get resolved. It is okay for migration to ignore prepare conflicts because it already captures all ongoing modifications to documents in the chunk range that will end up getting committed.

            Assignee:
            [DO NOT USE] Backlog - Cluster Scalability
            Reporter:
            Randolph Tan
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated: