Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Improve documentation for druid.coordinator.balancer.strategy option #17530

Open
rafitadiaz opened this issue Dec 2, 2024 · 2 comments · May be fixed by #17595
Open

Improve documentation for druid.coordinator.balancer.strategy option #17530

rafitadiaz opened this issue Dec 2, 2024 · 2 comments · May be fixed by #17595
Assignees

Comments

@rafitadiaz
Copy link

I see that in the configuration reference for the option druid.coordinator.balancer.strategy is mention that:

  • diskNormalized weights the costs according to the servers' disk usage ratios - there are known issues with this strategy distributing segments unevenly across the cluster.
  • random distributes segments among services randomly.

And then says that the default is cost.

What is cost? Cost base on what? Where can we find a reference on the documentation explaining the differences between 3 strategies?

It would be great a brief explanation of what is the cost strategy and why is the default

@kfaraz kfaraz self-assigned this Dec 21, 2024
@kfaraz kfaraz linked a pull request Dec 21, 2024 that will close this issue
@kfaraz
Copy link
Contributor

kfaraz commented Dec 21, 2024

Thanks for reporting this issue, @rafitadiaz !

I have created a PR #17595 to improve the docs.
You can see a preview here: https://github.com/apache/druid/blob/1105837763e7da29fba9f430dbe45d7d01618b5d/docs/design/coordinator.md#balancing-segments-in-a-tier

@rafitadiaz
Copy link
Author

Ooohhh. Thanks 🙏🙏🙏🙏

This is super helpful and very well explained.

Thanks for the update!!!!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants