[SERVER-39839] Clear WouldChangeOwningShard errors in batch writer once successfully move the doc 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 |
|
We need to clear the WouldChangeOwningShard errors that we track in the batch writer once we successfully move the document. Because we will handle a WCOS error immediately rather than re-targeting and looping back around in the batch writer, these errors will not be cleared in the same way the SSV or CannotImplicitlyCreateCollection errors are. We should add unit tests to as a part of this ticket. |