-
Notifications
You must be signed in to change notification settings - Fork 180
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
[feat][doc] add overview for broker load balancing #621
Conversation
sidebar_label: "Concepts" | ||
--- | ||
|
||
WIP. Stay tuned! |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is created by purpose, to notify users we're on it and will publish soon.
|
||
## Related topics | ||
|
||
- To learn essential fundamentals, see [Broker load balancing | Concepts](./concepts-broker-load-balancing-concepts.md). |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'll add more related topics once I finish more.
Hi @heesung-sn @Demogorgon314 @D-2-Ed you've already reviewed this doc in Doc | Broker Load Balancing (Overview), could you please review this PR? Feel free to approve it if no more comments, thanks! |
|
||
- At the persistence layer ([BookKeeper](https://bookkeeper.apache.org/)), message segments in topics are balanced across all the bookies in the cluster. When an individual bookie runs out of storage capacity, the rest segments are loaded into the available bookies. | ||
|
||
- At the serving layer ([broker](./concepts-architecture-overview.md#brokers)), topic rearrangement (balance) is seamless. Brokers do not need to copy messages from one broker to another when rebalancing topics among brokers. Instead, the current owner broker temporarily closes the topic and client sessions and transfers the ownership to the selected broker. Then, the selected broker takes ownership of the topic and opens the topic sessions to the clients. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
nit : [broker] -> [Broker]
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks! Here we should use "broker" rather than "Broker" since it's a normal noun.
@momo-jun @Huanli-Meng could you please help review? Thank you! |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Only one minor comment. LGTM
|
||
## Related topics | ||
|
||
- To learn essential fundamentals, see [broker load balancing | concepts](./concepts-broker-load-balancing-concepts.md). |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
broker load balancing concepts?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I use |
on purpose since there will be broker load balancing | use cases
, broker load balancing | benefits
, broker load balancing | workflow
... later.
Feel free to check related resources:
Doc IA | Broker load balancing
Doc Outline | Broker load balancing
doc
@heesung-sn @Demogorgon314 thanks for your detailed technical guidance!
@D-2-Ed thanks for your thorough editor review!