[SERVER-31627] ShardingTest.checkUUIDsConsistentAcrossCluster can fail to see collection in config.cache.collections Created: 18/Oct/17 Updated: 30/Oct/23 Resolved: 05/Dec/17 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | 3.5.13 |
| Fix Version/s: | 3.6.1, 3.7.1 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Randolph Tan | Assignee: | Esha Maharishi (Inactive) |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||
| Operating System: | ALL | ||||||||
| Backport Requested: |
v3.6
|
||||||||
| Sprint: | Sharding 2017-11-13, Sharding 2017-12-04, Sharding 2017-12-18 | ||||||||
| Participants: | |||||||||
| Linked BF Score: | 0 | ||||||||
| Description |
|
of the local shard because the entry is created asynchronously. |
| Comments |
| Comment by Githook User [ 05/Dec/17 ] | ||||||||
|
Author: {'username': 'EshaMaharishi', 'email': 'esha.maharishi@mongodb.com', 'name': 'Esha Maharishi'}Message: | ||||||||
| Comment by Githook User [ 05/Dec/17 ] | ||||||||
|
Author: {'username': 'EshaMaharishi', 'email': 'esha.maharishi@mongodb.com', 'name': 'Esha Maharishi'}Message: (cherry picked from commit 84b68e8459df1b795fa25eeaee05b76967eb9406) | ||||||||
| Comment by Githook User [ 05/Dec/17 ] | ||||||||
|
Author: {'username': 'EshaMaharishi', 'email': 'esha.maharishi@mongodb.com', 'name': 'Esha Maharishi'}Message: | ||||||||
| Comment by Esha Maharishi (Inactive) [ 05/Dec/17 ] | ||||||||
|
Note: this symptom (the shard not having an entry in its persisted cache for some sharded collection) may still appear in the config stepdown suite after this fix if the following occurs: 1) shardCollection runs on config primary, writes entry to config.collections, and entry propagates to another node If the test does not do anything else that would make the primary shard refresh, the primary shard will not have an entry for the collection in its config.cache.collections. This happened in my patch build: https://evergreen.mongodb.com/task/mongodb_mongo_master_enterprise_rhel_62_64_bit_sharding_csrs_continuous_config_stepdown_WT_patch_671dd2c46fb49aabd969781b3c8c90cb109a1032_5a25d327e3c33129d00121ff_17_12_04_22_58_54 You can see that setShardVersion was not sent for 'test.compound' in the logs:
|