[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: |
|
||||
| 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: |