-
Type: Bug
-
Resolution: Fixed
-
Priority: Major - P3
-
Affects Version/s: None
-
Component/s: Performance
Use Case
As a write concern 0 user
I want the driver to set the fire-and-forget bit
So that the server handles the unacknowledged write as expected
User Impact
- Has the potential to change the outcome of writes, operations that once would fail could now succeed.
Dependencies
- None
Acceptance Criteria
Implementation Requirements
- If the command being run has a writeConcern w setting of 0
- set the moreToCome bit on the outgoing OP_MSG message.
- return the command without waiting for a server response
Testing Requirements
- Integration:
- ensure if writeConcern w = 0 on the command,
- moreToCome bit is set in outgoing request
- commandSucceededEvent's reply only contain { ok: 1 }
- ensure if writeConcern w = 0 on the command,
- Unit:
- ensure if writeConcern w = 0 on the command, moreToCome is set in OP_MSG
Documentation Requirements
- Update TSDoc over "w" settings to mention the side-effect of setting w:0 on the protocol message.
Follow Up Requirements
- None
- has to be done before
-
NODE-6377 Remove noResponse option
- Backlog
- is related to
-
SERVER-88833 mongos generates a reply for writes sent by client with w:0
- Closed