Learning Path
Configure Broker Listeners to Separate Cluster Traffic
In a distributed system, managing network resources is crucial to maintaining quality of service. One useful way to manage network resources is to separate different kinds of network traffic.
Not Started
Watch a preview
Configure Broker Listeners to Separate Cluster Traffic
- 01:30:00
- Downloadable resources available
- Certificate of completion included
Details
Difficulty Level
Intermediate
Language
English
Completion time
01:30:00
In a distributed system, managing network resources is crucial to maintaining quality of service. One useful way to manage network resources is to separate different kinds of network traffic. Apache® Kafka uses the concept of *listeners* to segregate network traffic.
Here are some cases where it might be useful to create different listeners:
- Separate Kafka Broker replication traffic onto its own network interface so it doesn’t interfere with clients
- Give priority to traffic from the Kafka Controller for smoother cluster operation, even when a broker’s client request queue is full
- Use different ports, authentication mechanisms
- Migrate clients from one authentication mechanism to another
- Separate traffic from different networks