|
We could potentially add a section to the Oplog page to state that for any given attempted write operation, the oplog only updates if the write succeeds. Might need some framing e.g. with majority committed writes, a write that fails the majority acknowledgement can succeed and result in an oplog event, despite the write concern failure. Would need to confirm with replication team as to whether this is generally applicable behavior, or whether some commands always generate an oplog event even on failure.
Otherwise, we can update the behavior section of the delete command and its related shell helpers to include a little blurb on the topic.
We might as well do the same for the update commands, as I assume they have the same affect (an update command that finds no documents to modify results in no oplog entries). Will also touch base with query w.r.t. what other commands result in oplog entries.
|