kfaraz opened a new pull request, #14902:
URL: https://github.com/apache/druid/pull/14902

   ### Changes
   - Determine the default value of `balancerComputeThreads` based on number of 
coordinator cpus rather than number of segments. Even if the number of segments 
is low and we create more balancer threads, it doesn't hurt the system as 
threads would mostly be idle.
   - Remove unused field from `SegmentLoadQueueManager`
   
   ### Expected values
   - Clusters with ~1M segments typically work with Coordinators having 16 
cores or more. This would give us 8 balancer threads, which is the same as the 
current maximum.
   - On small clusters, even a single thread is enough to do the required 
balancing work.
   
   ---
   
   This PR has:
   
   - [ ] been self-reviewed.
      - [ ] using the [concurrency 
checklist](https://github.com/apache/druid/blob/master/dev/code-review/concurrency.md)
 (Remove this item if the PR doesn't have any relation to concurrency.)
   - [ ] added documentation for new or modified features or behaviors.
   - [ ] a release note entry in the PR description.
   - [ ] added Javadocs for most classes and all non-trivial methods. Linked 
related entities via Javadoc links.
   - [ ] added or updated version, license, or notice information in 
[licenses.yaml](https://github.com/apache/druid/blob/master/dev/license.md)
   - [ ] added comments explaining the "why" and the intent of the code 
wherever would not be obvious for an unfamiliar reader.
   - [ ] added unit tests or modified existing tests to cover new code paths, 
ensuring the threshold for [code 
coverage](https://github.com/apache/druid/blob/master/dev/code-review/code-coverage.md)
 is met.
   - [ ] added integration tests.
   - [ ] been tested in a test Druid cluster.
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to