[SERVER-24828] ShardingCatalogClientImpl::_runBatchWriteCommand should notify the ReplicaSetMonitor for errors in the "writeErrors" response Created: 28/Jun/16 Updated: 06/Dec/22 Resolved: 30/Jun/16 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Kaloian Manassiev | Assignee: | [DO NOT USE] Backlog - Sharding Team |
| Resolution: | Duplicate | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Assigned Teams: |
Sharding
|
||||||||
| Operating System: | ALL | ||||||||
| Participants: | |||||||||
| Description |
|
The ShardingCatalogClientImpl::_runBatchWriteCommand call does retries but relies on the underlying ShardRemote instance to notify the ReplicaSetMonitor. There are errors, however, which are only included in the writeErrors field and thus we will miss informing the RSM. |
| Comments |
| Comment by Spencer Brody (Inactive) [ 28/Jun/16 ] |
|
Probably best done as part of |