Loading...

XML

Word

Printable

JSON

Type: Task
Resolution: Fixed
Priority: Major - P3
Fix Version/s: 7.2.0-rc0
Affects Version/s: None
Component/s: None
Labels:
- milestone-2

Assigned Teams:

Replication
Backwards Compatibility:
Fully Compatible
Sprint:
Repl 2023-08-07, Repl 2023-08-21, Repl 2023-09-04, Repl 2023-09-18
Confidence Status:
None
Work Order:
3
CAR Domain/s:
None

Aha! Reference:
None
Tracking Level:
None
Risk Status:
None
Exec Notes:
None
Goal Name(s):
None
Goal Link:
None

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.

depends on

SERVER-72792 Implement progress bookkeeping for individual ops in BulkWriteExec

Closed

related to

SERVER-78311 MongoS does not report writeConcernError in presence of writeErrors for insert command

Closed

SERVER-80918 Handle mongos retryable timeseries update WriteConcernErrors

Closed

Assignee:: Vishnu Kaushik
Reporter:: Vishnu Kaushik
Participants:: Githook User, Sean Zimmerman, Vishnu Kaushik
Votes:: 0 Vote for this issue
Watchers:: 7 Start watching this issue

Created:: May 09 2023 05:28:43 PM UTC
Updated:: Oct 29 2023 09:21:46 PM UTC
Resolved:: Sep 15 2023 02:31:51 PM UTC
Confidence Status Last Update:: 01/Aug/23 6:22 PM