|
Author:
{'name': 'Jason Chan', 'username': 'jasonjhchan', 'email': 'jason.chan@10gen.com'}
Message: SERVER-39438 Write "abortTransaction" oplog entry when aborting unprepared transactions with replicated operations
Branch: master
https://github.com/mongodb/mongo/commit/02b4ea3a929731cb34a3eeb3190051da42e1f2d3
|
|
As part of this ticket, we should also finish up this TODO to change the conditional into an invariant.
|
|
As tess.avitabile pointed out, if the oplog entries are written in a single WUOW, we don't have to write an "abort" oplog entry on unprepared "commit" or "prepare" failures, so I'm reprioritizing this ticket. We will need this if we decided to split the single WUOW into smaller ones for performance reason.
|
|
As pointed by tess.avitabile, if we cannot write an abort oplog entry, then we must fassert, unless we are no longer primary.
|
|
As part of this ticket, we should use OperationContext::runWithoutInterruption(Callback&& cb) to wrap the call into OpObserver::onTransactionAbort() since writing the "abort" oplog entry may fail otherwise due to interruption.
|
Generated at Thu Feb 08 04:52:04 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.