[SERVER-36513] Add testing in $out for staleShardVersion errors when writing to remote hosts Created: 07/Aug/18 Updated: 06/Dec/22 Resolved: 19/Sep/18 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Aggregation Framework |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Nicholas Zolnierz | Assignee: | Backlog - Query Team (Inactive) |
| Resolution: | Won't Fix | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Assigned Teams: |
Query
|
||||||||
| Participants: | |||||||||
| Comments |
| Comment by Charlie Swanson [ 19/Sep/18 ] |
|
We believe we have sufficient coverage via the work in Another interesting case which can lead to a stale shard version error is when the shard is stale because of a node restart. This may be worth testing in some capacity, but we do not expect to have any custom code to handle this within $out and therefore do not plan to do this work as part of that project. We have not checked, there may be tests for this case already for the ClusterWriter. |