SERVER-138010Open
Committed transactions report a spurious writeConcernError when a session kill interrupts the majority write-concern wait
A transaction that commits successfully can still report a {{{}writeConcernError{}}}(WCE) if a session kill delivered an interrupt to the committing operation before its majority write-concern wait completed. The interrupt is sticky and cannot be retracted, so the client receives {{ok: 1}} with WCE on a transaction that is durably committed. Retrying the whole operation in response is unsafe because the write already committed. h3. Why the error is not recoverable for clients as-is? [{{Tempo