[SERVER-39838] Track WouldChangeOwningShard exceptions in the batch writer Created: 26/Feb/19 Updated: 27/Oct/23 Resolved: 04/Apr/19 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Janna Golden | Assignee: | [DO NOT USE] Backlog - Sharding Team |
| Resolution: | Gone away | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Assigned Teams: |
Sharding
|
| Participants: |
| Description |
|
In order to handle WouldChangeOwningShard exceptions thrown for updates that are not part of a multi-stmt txn, we need to track these errors in the same way we track StaleShardVersion and CannotImplicitlyCreateCollection errors. |