[SERVER-21765] Sharding balancer should check for shutdown more frequently Created: 03/Dec/15 Updated: 06/Dec/22 Resolved: 12/Dec/16 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Kaloian Manassiev | Assignee: | [DO NOT USE] Backlog - Sharding Team |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Assigned Teams: |
Sharding
|
||||
| Operating System: | ALL | ||||
| Participants: | |||||
| Description |
|
The mongos clean shutdown sequence blocks waiting for all currently held distributed locks to be freed in order to proceed with the shutdown. This means that if the balancer takes long time to complete the round it would block shutdown. For this reason the balancer should be checking whether shutdown has been requested after each chunk has been migrated instead of once for the entire round. |
| Comments |
| Comment by Andy Schwerin [ 12/Dec/16 ] |
|
As of 3.4, the balancer doesn't run on mongos anymore, and so no longer blocks mongos shutdown. |