[SERVER-43201] Allow refine_collection_shard_key_basic.js to have more than one config.changelogs entry after completion of refine command, to account for stepdowns Created: 06/Sep/19  Updated: 29/Oct/23  Resolved: 09/Sep/19

Status: Closed
Project: Core Server
Component/s: Sharding
Affects Version/s: None
Fix Version/s: 4.3.1

Type: Bug Priority: Major - P3
Reporter: Blake Oler Assignee: Blake Oler
Resolution: Fixed Votes: 0
Labels: sharding-csrs-stepdown-upkeep
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
Backwards Compatibility: Fully Compatible
Operating System: ALL
Sprint: Sharding 2019-09-09
Participants:
Linked BF Score: 0

 Description   

If there is a stepdown during the middle of a refineCollectionShardKey command, it's possible for the config server to eventually commit more than one entry to the config.changelog collection for starting the refine command. We should change the check to be equal to or greater than instead of equal to.



 Comments   
Comment by Githook User [ 09/Sep/19 ]

Author:

{'name': 'Blake Oler', 'username': 'BlakeIsBlake', 'email': 'blake.oler@mongodb.com'}

Message: SERVER-43201 Allow refine_collection_shard_key_basic.js to have more than one config.changelogs entry after completion of refine command, to account for stepdowns
Branch: master
https://github.com/mongodb/mongo/commit/0eb3337d580b7a9f486ee6157be0bc68e6ef4a38

Generated at Thu Feb 08 05:02:32 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.