[SERVER-68843] Write concern accepts negative values for w argument Created: 15/Aug/22 Updated: 05/Dec/22 Resolved: 15/Aug/22 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Ali Mir | Assignee: | Backlog - Replication Team |
| Resolution: | Won't Fix | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Assigned Teams: |
Replication
|
| Operating System: | ALL |
| Participants: |
| Description |
|
In 4.2, we don't have strict bounds checking for the w argument for write concern. Instead, we only throw an error if the value is 0. This allows negative values for w (effectively unacknowledged writes). If we decide to fix this, we should disallow negative values to be passed into write concern. |
| Comments |
| Comment by Opal Hoyt [ 15/Aug/22 ] |
|
Not considering a fix worth the risk of issues – also closing in on EOL for 4.2 |