Make sure chunk migration can handle a retryable internal transaction whose oplog entries have been truncated

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Fixed
    • Priority: Major - P3
    • 7.0.0-rc0, 6.0.5, 6.3.0-rc1
    • Affects Version/s: None
    • Component/s: None
    • None
    • Fully Compatible
    • ALL
    • v6.3, v6.0
    • Sharding NYC 2023-02-20
    • 147
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      It is incorrect to invariant that a retryable internal transaction can only applyOps oplog entry since if the TransactionHistoryIterator::next() would throw an IncompleteTransactionHistory error if the oplog entry cannot be found (e.g. has been removed due to oplog truncation). Please see BF-27708 for more details.

              Assignee:
              Cheahuychou Mao
              Reporter:
              Cheahuychou Mao
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

                Created:
                Updated:
                Resolved: