[SERVER-83829] Mongos can incorrectly report WCE after a retry of WriteWithoutShardKeyWithID writes despite succeeding in second try Created: 02/Dec/23 Updated: 10/Jan/24 Resolved: 10/Jan/24 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 7.3.0-rc0 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Abdul Qadeer | Assignee: | Abdul Qadeer |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Assigned Teams: |
Cluster Scalability
|
| Backwards Compatibility: | Fully Compatible |
| Operating System: | ALL |
| Sprint: | Cluster Scalability 2024-1-8, Cluster Scalability 2024-1-22 |
| Participants: |
| Description |
|
Under PM-3190, as reported by kaitlin.mahar@mongodb.com verbatim:
|
| Comments |
| Comment by Githook User [ 10/Jan/24 ] |
|
Author: {'name': 'Abdul Qadeer', 'email': 'abdul.qadeer@mongodb.com', 'username': 'zorro786'}Message: GitOrigin-RevId: 2a53d7cb226d1912f154aa59563759148795f28a |
| Comment by Kaitlin Mahar [ 04/Dec/23 ] |
|
I am fixing this on the bulkWrite codepath in |
| Comment by Abdul Qadeer [ 02/Dec/23 ] |
|
This scenario is possible for no-op writes. A solution would be to mark the WCE in a broadcast and later clear it if any further retry has to happen for the write. |