Red Hat Summit이 콘텐츠는 선택한 언어로 제공되지 않습니다.
Chapter 7. Brokers page
The Brokers page shows all the brokers created for a Kafka cluster. For each broker, you can see its status, as well as the distribution of partitions across the brokers, including the number of partition leaders and followers.
The broker status is shown as one of the following:
- Not Running
- The broker has not yet been started or has been explicitly stopped.
- Starting
- The broker is initializing and connecting to the cluster, including discovering and joining the metadata quorum.
- Recovery
- The broker has joined the cluster but is in recovery mode, replicating necessary data and metadata before becoming fully operational. It is not serving clients.
- Running
- The broker is fully operational, registered with the controller, and actively serving client requests.
- Pending Controlled Shutdown
- The broker has initiated a controlled shutdown process and will shut down gracefully once complete.
- Shutting Down
- The broker is in the process of shutting down. Client connections are being closed, and internal resources are being released.
- Unknown
- The broker’s state is unknown, possibly due to an unexpected error or failure.
If the broker has a rack ID, this is the ID of the rack or datacenter in which the broker resides.
Click on the right arrow (>) next to a broker name to see more information about the broker, including its hostname and disk usage.
Click on the Rebalance tab to show any rebalances taking place on the cluster.
Consider rebalancing if the distribution is uneven to ensure efficient resource utilization.
7.1. Managing rebalances
When you configure KafkaRebalance resources to generate optimization proposals on a cluster, you can check their status from the Rebalance tab. The Rebalance tab presents a chronological list of KafkaRebalance resources from which you can manage the optimization proposals.
Cruise Control must be enabled to run alongside the Kafka cluster in order to use the Rebalance tab. For more information on setting up and using Cruise Control to generate proposals, see the Streams for Apache Kafka documentation.
Procedure
- From the Streams for Apache Kafka Console, log in to the Kafka cluster, then click Brokers.
Check the information on the Rebalance tab.
For each rebalance, you can see its status and a timestamp in UTC.
Expand Table 7.1. Rebalance status descriptions Status Description NewResource has not been observed by the operator before
PendingProposalOptimization proposal not generated
ProposalReadyOptimization proposal is ready for approval
RebalancingRebalance in progress
StoppedRebalance stopped
NotReadyError ocurred with the rebalance
ReadyRebalance complete
ReconciliationPausedRebalance is paused
NoteThe status of the
KafkaRebalanceresource changes toReconciliationPausedwhen thestrimzi.io/pause-reconciliationannotation is set totruein its configuration.- Click on the right arrow (>) next to a rebalance name to see more information about the broker, including its rebalance mode, and whether auto-approval is enabled. If the rebalance involved brokers being removed or added, they are also listed.
Optimization proposals can be generated in one of three modes:
-
fullis the default mode and runs a full rebalance. -
add-brokersis the mode used after adding brokers when scaling up a Kafka cluster. -
remove-brokersis the mode used before removing brokers when scaling down a Kafka cluster.
If auto-approval is enabled for a proposal, a successfully generated proposal goes straight into a cluster rebalance.
Viewing optimization proposals
Click on the name of a KafkaRebalance resource to see a generated optimization proposal. An optimization proposal is a summary of proposed changes that would produce a more balanced Kafka cluster, with partition workloads distributed more evenly among the brokers.
For more information on the properties shown on the proposal and what they mean, see the Streams for Apache Kafka documentation.
Managing rebalances
Select the options icon (three vertical dots) and click on an option to manage a rebalance.
-
Click Approve to approve a proposal.
The rebalance outlined in the proposal is performed on the Kafka cluster. -
Click Refresh to generate a fresh optimization proposal.
If there has been a gap between generating a proposal and approving it, refresh the proposal so that the current state of the cluster is taken into account with a rebalance. -
Click Stop to stop a rebalance.
Rebalances can take a long time and may impact the performance of your cluster. Stopping a rebalance can help avoid performance issues and allow you to revert changes if needed.
The options available depend on the status of the KafkaBalance resource. For example, it’s not possible to approve an optimization proposal if it’s not ready.
'%20d='M201.5%20305.5c-13.8%200-24.9-11.1-24.9-24.6%200-13.8%2011.1-24.9%2024.9-24.9%2013.6%200%2024.6%2011.1%2024.6%2024.9%200%2013.6-11.1%2024.6-24.6%2024.6zM504%20256c0%20137-111%20248-248%20248S8%20393%208%20256%20119%208%20256%208s248%20111%20248%20248zm-132.3-41.2c-9.4%200-17.7%203.9-23.8%2010-22.4-15.5-52.6-25.5-86.1-26.6l17.4-78.3%2055.4%2012.5c0%2013.6%2011.1%2024.6%2024.6%2024.6%2013.8%200%2024.9-11.3%2024.9-24.9s-11.1-24.9-24.9-24.9c-9.7%200-18%205.8-22.1%2013.8l-61.2-13.6c-3-.8-6.1%201.4-6.9%204.4l-19.1%2086.4c-33.2%201.4-63.1%2011.3-85.5%2026.8-6.1-6.4-14.7-10.2-24.1-10.2-34.9%200-46.3%2046.9-14.4%2062.8-1.1%205-1.7%2010.2-1.7%2015.5%200%2052.6%2059.2%2095.2%20132%2095.2%2073.1%200%20132.3-42.6%20132.3-95.2%200-5.3-.6-10.8-1.9-15.8%2031.3-16%2019.8-62.5-14.9-62.5zM302.8%20331c-18.2%2018.2-76.1%2017.9-93.6%200-2.2-2.2-6.1-2.2-8.3%200-2.5%202.5-2.5%206.4%200%208.6%2022.8%2022.8%2087.3%2022.8%20110.2%200%202.5-2.2%202.5-6.1%200-8.6-2.2-2.2-6.1-2.2-8.3%200zm7.7-75c-13.6%200-24.6%2011.1-24.6%2024.9%200%2013.6%2011.1%2024.6%2024.6%2024.6%2013.8%200%2024.9-11.1%2024.9-24.6%200-13.8-11-24.9-24.9-24.9z'/%3e%3c/svg%3e){kind=small}