[SERVER-54158] Missing shard metadata refresh from the CS in coll_timestamp_test.js Created: 30/Jan/21 Updated: 29/Oct/23 Resolved: 05/Feb/21 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | None |
| Fix Version/s: | 4.9.0 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Sergi Mateo Bellido | Assignee: | Sergi Mateo Bellido |
| 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 | ||||
| Sprint: | Sharding 2021-02-08 | ||||
| Participants: | |||||
| Linked BF Score: | 12 | ||||
| Description |
|
The underlying issue is that the test is assuming that after the refineShardKey command the persistent cached metadata on the shards is updated. However, the test is not forcing a refresh so those changes are not visible. In order to fix that we could add an explicit refresh of the collection before checking that the timestamp in config.cache.collections (shard) is the same as in config.collections (config server). |
| Comments |
| Comment by Githook User [ 05/Feb/21 ] |
|
Author: {'name': 'Sergi Mateo Bellido', 'email': 'sergi.mateo-bellido@mongodb.com', 'username': 'smateo'}Message: |