[SERVER-62268] Handle balancer configuration refresh in `balancer_defragmentation_merge_chunks.js` Created: 24/Dec/21 Updated: 29/Oct/23 Resolved: 10/Jan/22 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 5.3.0 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Pierlauro Sciarelli | Assignee: | Tommaso Tocci |
| 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 | ||||
| Participants: | |||||
| Linked BF Score: | 134 | ||||
| Description |
|
When shards are refreshing the balancer configuration from the CSRS (every 30 seconds), some reads are performed on `config.settings` to retrieve the current state of the balancer. It is then possible that a shards temporarily has a non-updated status of the balancer for 30 seconds. For example, it can happen that a shard believes the auto splitter had been disabled because a refresh can see the stop of the balancer and not the subsequent start. |
| Comments |
| Comment by Githook User [ 05/Jan/22 ] |
|
Author: {'name': 'Tommaso Tocci', 'email': 'tommaso.tocci@mongodb.com', 'username': 'toto-dev'}Message: |