[SERVER-32694] Retry find on StaleShardVersion in sharding_balance4.js Created: 12/Jan/18 Updated: 06/Dec/22 Resolved: 18/Jan/18 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Jack Mulrow | 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: | |||||||||||||
| Linked BF Score: | 15 | ||||||||||||
| Description |
|
sharding_balance4.js occasionally fails because more than 10 migrations complete during the course of a find command exhausting mongos's retry attempts and failing the test. Modifying the test to retry a couple times on StaleShardVersion should make it fail less often. We can also consider making a generic override for read commands that retry on StaleShardVersion errors, so it can be load-ed into tests that involve frequent migrations. |