[SERVER-72790] Handle stale config errors and refresh targeters for bulkWrite Created: 12/Jan/23 Updated: 27/Oct/23 Resolved: 03/Jun/23 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Lingzhi Deng | Assignee: | Backlog - Replication Team |
| Resolution: | Gone away | Votes: | 0 |
| Labels: | milestone-2 | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||||||
| Assigned Teams: |
Replication
|
||||||||||||||||||||
| Participants: | |||||||||||||||||||||
| Description |
|
When mongos receives a bulkWrite response from a shard, it needs to iterate through the response cursor and look for StaleConfig / StaleDbVersion errors. If anything was stale for a particular namespace, we will need to note down the error and mongos needs to refresh the targeters before retargeting the remaining operations. This is similar to what we currently have (this and this) in BatchWriteExec. |
| Comments |
| Comment by Vishnu Kaushik [ 03/Jun/23 ] |
|
Done within |