because the oplog rolled over. This shouldn't cause the migration to fail, as this might just be a session that is too old that the user won't ever reference it again. However, the recipient shard should also have a way of knowing that it has accepted an incomplete history so when it can error our appropriately when the user attempts to perform a retryable write on the same transaction.
- Votes:
-
0 Vote for this issue
- Watchers:
-
1 Start watching this issue
- Created:
- Updated:
- Resolved: