WriteConcernError

Python (PyMongo)OperationFailurewrite

Raised when a write operation succeeds but the write concern was not satisfied

Related Jira Issues

NODE-7914Investigating
Mandate raising writeConcernError (change SHOULD to MUST)
This ticket was split from {{{}DRIVERS-3684{}}}, please see that ticket for a detailed description. h3. Expected Behavior As a... _(who is this affects)_ I expect... _(describe behavior)_ When... _(trigger action)_ h3. Actual Behavior and Impact * _What is the actual behavior?_ * _If bug: What is the number of impacted customers? How severe is the impact? Is anyone blocked or broken?_ h3. Dependencies * _upstream and/or downstream requirements and timelines to bear in mind_
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
SERVER-125892Blocked
Add HostUnreachable to retryable errors in implicitly_retry_on_config_stepdowns.js override
Root Cause: SERVER-108482 correctly removed the isNotPrimaryError retry from kNotIdempotent in Shard::remoteIsRetriableError, which had previously masked config-stepdown errors by silently retrying setDefaultRWConcern at the C++ layer before they reached the JS test layer. With that safety net gone, when the config primary steps down during write-concern satisfaction of setDefaultRWConcern, the response surfaces as writeConcernError: "code: 6, HostUnreachable, "operation was interrupted" ": an
JAVA-6345Closed
Mandate raising writeConcernError (change SHOULD to MUST)
This ticket was split from {{DRIVERS-3684}}, please see that ticket for a detailed description.
CSHARP-6271In Code Review
Mandate raising writeConcernError (change SHOULD to MUST)
This ticket was split from {{DRIVERS-3684}}, please see that ticket for a detailed description.
PYTHON-6181Closed
Mandate raising writeConcernError (change SHOULD to MUST)
This ticket was split from {{DRIVERS-3684}}, please see that ticket for a detailed description.
GODRIVER-4196Ready for Work
Mandate raising writeConcernError (change SHOULD to MUST)
This ticket was split from {{DRIVERS-3684}}, please see that ticket for a detailed description.
GODRIVER-4025Closed
fix: Preserve first writeConcernError in unordered bulk write
h3. *Context* An unordered collection.BulkWrite that spans multiple batches can silently return success when an earlier batch's write-concern failure is overwritten by a later successful batch's nil WriteConcernError. This is collection bulk-write, not client bulk-write. In triage, we assumed client bulk-write which [prohibits propagating batch errors|https://github.com/mongodb/specifications/blob/master/source/crud/bulk-write.md#write-concern-errors]. Collection bulk-write does not have t
JAVA-5125Backlog
Some write concern errors are not retried according to spec
JAVA-5124 was opened because the legacy retryable writes test suite was not being run against sharded clusters. After that issue was addressed it was observed that tests of write concern error retryability fail on 4.2 and 4.4 sharded clusters. The tests that fail mostly have description ending with "succeeds after WriteConcernError ShutdownInProgress", although there are a few other failures as well. While attempting to debug these test failures, the following observations were made: 1.
JAVA-6087In Code Review
RetryableWriteError label not preserved for retryable writeConcernError
In MixedBulkWriteOperation, when we decide to attach RetryableWriteError for a retryable write concern failure (e.g., last-attempt path), the label is currently written to the {*}writeConcernErro{*}r subdocument. However, when building MongoBulkWriteException, BulkWriteBatch.getBulkWriteException() reads labels from the top-level {*}result.errorLabels{*}. Labels added under *writeConcernError* are not parsed, so they are lost. *Impact* Applications checking e.hasErrorLabel("RetryableWriteErr