[SERVER-38717] Shell should prohibit unacknowledged writes in session Created: 20/Dec/18 Updated: 29/Oct/23 Resolved: 15/Jan/19 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Shell |
| Affects Version/s: | None |
| Fix Version/s: | 4.1.7 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | A. Jesse Jiryu Davis | Assignee: | A. Jesse Jiryu Davis |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Operating System: | ALL | ||||||||
| Sprint: | Repl 2019-01-14, Repl 2019-01-28 | ||||||||
| Participants: | |||||||||
| Description |
|
The Driver Sessions Spec says: "For unacknowledged writes with an explicit session, drivers SHOULD raise an error. If a driver allows users to provide an explicit session with an unacknowledged write (e.g. for backwards compatibility), the driver MUST NOT send the session ID." As demonstrated in shell_can_retry_writes.js and perhaps other places, the shell allows w: 0 writes in an explicit session. It therefore risks exactly what the spec wants to prevent: concurrent writes with the same lsid. |
| Comments |
| Comment by Githook User [ 15/Jan/19 ] |
|
Author: {'username': 'ajdavis', 'email': 'jesse@mongodb.com', 'name': 'A. Jesse Jiryu Davis'}Message: |