[SERVER-31668] checkUUIDsConsistentAcrossCluster must retry on NotMaster errors Created: 20/Oct/17 Updated: 06/Dec/22 Resolved: 15/Sep/21 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | None |
| Fix Version/s: | 4.3 Desired |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Dianna Hohensee (Inactive) | Assignee: | [DO NOT USE] Backlog - Sharding EMEA |
| Resolution: | Won't Do | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||||||
| Assigned Teams: |
Sharding EMEA
|
||||||||||||||||||||
| Sprint: | Sharding 2017-12-04, Sharding 2017-12-18 | ||||||||||||||||||||
| Participants: | |||||||||||||||||||||
| Linked BF Score: | 15 | ||||||||||||||||||||
| Description |
|
The UUID check is failing because slow machines can cause unexpected shard primary step downs, and the UUID check does listCollections directly against the shard, which only runs on a primary and returns NotMaster if the expected primary is no longer primary.
|
| Comments |
| Comment by Esha Maharishi (Inactive) [ 02/Oct/19 ] |
|
Updating the fix version to 4.3 desired so it is easier to find in the list of high-ish priority sharding tickets. |
| Comment by Dianna Hohensee (Inactive) [ 10/Nov/17 ] |
|
This is probably going to be a very similar to |