[SERVER-56323] resharding_collection_cloner*.js tests must wait for config.cache.chunks to be persisted Created: 23/Apr/21 Updated: 29/Oct/23 Resolved: 24/Apr/21 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | None |
| Fix Version/s: | 5.0.0-rc0 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Max Hirschhorn | Assignee: | Max Hirschhorn |
| 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 | ||||
| Sprint: | Sharding 2021-05-03 | ||||
| Participants: | |||||
| Linked BF Score: | 141 | ||||
| Story Points: | 1 | ||||
| Description |
|
The _shardsvrShardCollection command doesn't wait for the config.cache.chunks entries to have been written on itself (i.e. the primary shard for the database). Note that while _flushRoutingTableCacheUpdates would wait for the config.cache.chunks entries to have been written, the _flushRoutingTableCacheUpdates command is only run by the primary shard for the database on all of the other shards owning chunks for the now-sharded collection. The resharding_collection_cloner*.js tests should be updated to explicitly run the {_flushRoutingTableCacheUpdates: temporaryReshardingCollection.getFullName()} command on the shards. |
| Comments |
| Comment by Githook User [ 24/Apr/21 ] |
|
Author: {'name': 'Max Hirschhorn', 'email': 'max.hirschhorn@mongodb.com', 'username': 'visemet'}Message: |