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

[Enhancement] Support slow broker detect on AutoBalancer #1120

Closed
SCNieh opened this issue Apr 15, 2024 · 0 comments
Closed

[Enhancement] Support slow broker detect on AutoBalancer #1120

SCNieh opened this issue Apr 15, 2024 · 0 comments
Assignees
Labels
enhancement New feature or request

Comments

@SCNieh
Copy link
Contributor

SCNieh commented Apr 15, 2024

What's the problem

When a broker experiences internal issues and has increased latency in producing or fetching data, the network bandwidth is likely to decrease. To ensure load balance within the cluster, the AutoBalancer will attempt to assign additional partitions to this broker, which can result in more partitions being affected by the failure.

How to identify slow brokers

Brokers will need to reporter additional metrics including append latency, append stream queue size, fast read latency and fetch queue size. And AutoBalancer will mark a broker as "slow" If any of these metrics show a sudden increase compared to the historical statistics

What to do with slow brokers

When a broker is marked as "slow", there will be no more additional partitions assigned to this broker. However, moving out existing partitions form it is still allowed.

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

No branches or pull requests

1 participant