[SERVER-50635] Index consistency check at end of sharding tests isn't robust to ShardNotFound Created: 29/Aug/20 Updated: 29/Oct/23 Resolved: 08/Sep/20 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding, Testing Infrastructure |
| Affects Version/s: | None |
| Fix Version/s: | 4.7.0, 4.4.2 |
| Type: | Bug | Priority: | Minor - P4 |
| Reporter: | Max Hirschhorn | Assignee: | Jack Mulrow |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | sharding-wfbf-day | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||
| Operating System: | ALL | ||||||||
| Backport Requested: |
v4.4
|
||||||||
| Sprint: | Sharding 2020-09-21 | ||||||||
| Participants: | |||||||||
| Linked BF Score: | 0 | ||||||||
| Description |
|
The balancing_sessions_collection.js intentionally removes one of the shards before shutting down the ShardingTest. It is possible for mongos to refresh its ShardRegistry after choosing to target all shards with the $indexStats aggregation and then triggers a ShardNotFound error. One proposal to address this issue is to retry running the $indexStats aggregation on ShardNotFound errors. |
| Comments |
| Comment by Githook User [ 18/Sep/20 ] |
|
Author: {'name': 'Jack Mulrow', 'email': 'jack.mulrow@mongodb.com', 'username': 'jsmulrow'}Message: (cherry picked from commit 24ce8e9b42bc34d111999f516b8c5b2abedb8892) |
| Comment by Githook User [ 08/Sep/20 ] |
|
Author: {'name': 'Jack Mulrow', 'email': 'jack.mulrow@mongodb.com', 'username': 'jsmulrow'}Message: |