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.
Make sure chunk migration can handle a retryable internal transaction whose oplog entries have been truncated
- Votes:
-
0 Vote for this issue
- Watchers:
-
4 Start watching this issue
- Created:
- Updated:
- Resolved: