[SERVER-80890] _configsvrCommitRefineCollectionShardKey test should wait for the metadata to be fully replicated Created: 08/Sep/23 Updated: 29/Oct/23 Resolved: 08/Sep/23 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | None |
| Fix Version/s: | 7.2.0-rc0, 7.1.0-rc2 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Marcos José Grillo Ramirez | Assignee: | Marcos José Grillo Ramirez |
| 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: |
v7.1
|
||||||||||||||||
| Sprint: | Sharding EMEA 2023-09-18 | ||||||||||||||||
| Participants: | |||||||||||||||||
| Linked BF Score: | 35 | ||||||||||||||||
| Description |
|
configsvr_commit_refine_collection_shard_key.js is doing a refresh in the shard in order to leave consistent metadata for the CheckShardFilteringMetadata hook, however, because there is no communication between the shard and the config server, the configOpTime is not being properly propagated, and if the refresh hits a secondary node that haven't replicated the metadata, we'll find inconsistencies when running the hook. We could wait for the config server to fully replicate the changes before issuing the refresh. |
| Comments |
| Comment by Githook User [ 08/Sep/23 ] |
|
Author: {'name': 'Marcos José Grillo Ramirez', 'email': 'marcos.grillo@mongodb.com', 'username': 'm4nti5'}Message: (cherry picked from commit edbb2e57fe1f3cda3d7a2899e23142d4dbd9c3f1) |
| Comment by Githook User [ 08/Sep/23 ] |
|
Author: {'name': 'Marcos José Grillo Ramirez', 'email': 'marcos.grillo@mongodb.com', 'username': 'm4nti5'}Message: |