[SERVER-76954] Support write concern and handle write concern errors on mongos Created: 09/May/23 Updated: 29/Oct/23 Resolved: 15/Sep/23 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 7.2.0-rc0 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Vishnu Kaushik | Assignee: | Vishnu Kaushik |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | milestone-2 | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||||||
| Assigned Teams: |
Replication
|
||||||||||||||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||||||||||||||
| Sprint: | Repl 2023-08-07, Repl 2023-08-21, Repl 2023-09-04, Repl 2023-09-18 | ||||||||||||||||||||
| Participants: | |||||||||||||||||||||
| Description |
|
It's possible for a bulk write command sent to a shard may return with a write concern error. We need to handle that case. |
| Comments |
| Comment by Githook User [ 14/Sep/23 ] |
|
Author: {'name': 'kauboy26', 'email': 'vishnu.kaushik@mongodb.com', 'username': 'kauboy26'}Message: |
| Comment by Sean Zimmerman [ 21/Jun/23 ] |
|
Since |
| Comment by Vishnu Kaushik [ 21/Jun/23 ] |
|
Yeah, maybe there's an existing way. Batch write exec (existing mongos implementation) also defines it and then parses it by hand. It's unfortunate that writeConcernError has been singled out. It's because it's missing from the list of other general arguments; see SERVER-77798. |