[SERVER-64437] Improve the logic to consume streaming actions on the Balancer secondary thread Created: 11/Mar/22 Updated: 29/Oct/23 Resolved: 24/Mar/22 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 6.0.0-rc0 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Paolo Polato | Assignee: | Paolo Polato |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||||||||||
| Sprint: | Sharding EMEA 2022-04-04 | ||||||||||||||||
| Participants: | |||||||||||||||||
| Description |
|
The secondary thread of the balancer is meant to retrieve a stream of defragmentation command descriptors from the defragmentation policy, and to be put on pause when there is no new activity to be consumed. The logic to suspend/resume the action of the thread is currently implemented within the policy, and it could be greatly simplified if it were brought back to the balancer (improving separation of concerns and allowing to create a generic synch infrastructure that could be reused to implement |
| Comments |
| Comment by Githook User [ 24/Mar/22 ] |
|
Author: {'name': 'Paolo Polato', 'email': 'paolo.polato@mongodb.com', 'username': 'ppolato'}Message: |