[SERVER-34907] updates to config.cache.collections/chunks can get lost when a node steps down Created: 08/May/18 Updated: 27/Oct/23 Resolved: 18/Feb/22 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Randolph Tan | Assignee: | [DO NOT USE] Backlog - Sharding EMEA |
| Resolution: | Works as Designed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Assigned Teams: |
Sharding EMEA
|
||||
| Operating System: | ALL | ||||
| Participants: | |||||
| Linked BF Score: | 15 | ||||
| Description |
|
Pending tasks will simply be removed because of this condition. |
| Comments |
| Comment by Kaloian Manassiev [ 18/Feb/22 ] |
|
Shards do not rely on the contents of the cache collections in order to know what is their version. They always need to recover that from the config server. |
| Comment by Randolph Tan [ 09/May/18 ] |
|
kaloian.manassiev, that is for the specific build failure where this bug was discovered. However, I think this can also trigger other bugs that we found related to shards failing to persist that it has a newer version. For example, |
| Comment by Kaloian Manassiev [ 08/May/18 ] |
|
Is the effect of this bug only that the UUID validation at the end of the test will fail for the secondaries, because the cache entries weren't written? If this is the case, given that rs_stepdown_and_pooling.js we should just blacklist it so it doesn't do UUID validation. |