Uploaded image for project: 'Core Server'
  1. Core Server
  2. SERVER-73938

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

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

      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@mongodb.com Cheahuychou Mao
            Reporter:
            cheahuychou.mao@mongodb.com Cheahuychou Mao
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: