[
https://issues.apache.org/jira/browse/KAFKA-4565?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ismael Juma updated KAFKA-4565:
-------------------------------
Description:
During the 0.9.0.0 release cycle, support for multiple listeners per broker was
introduced (KAFKA-1809). Each listener is associated with a security protocol,
ip/host and port. When combined with the advertised listeners mechanism, there
is a fair amount of flexibility with one limitation: at most one listener per
security protocol in each of the two configs (listeners and
advertised.listeners).
In some environments, one may want to differentiate between external clients,
internal clients and replication traffic independently of the security protocol
for cost, performance and security reasons. See the KIP for more details:
https://cwiki.apache.org/confluence/display/KAFKA/KIP-103%3A+Separation+of+Internal+and+External+traffic
was:
During the 0.9.0.0 release cycle, support for multiple listeners per broker was
introduced (KAFKA-1809). Each listener is associated with a security protocol,
ip/host and port. When combined with the advertised listeners mechanism, there
is a fair amount of flexibility with one limitation: at most one listener per
security protocol in each of the two configs (listeners and
advertised.listeners).
In some environments, one may want to differentiate between external clients,
internal clients and replication traffic independently of the security protocol
for cost, performance and security reasons. See the KIP for more details:
https://cwiki.apache.org/confluence/display/KAFKA/KIP-103%3A+Separate+Internal+and+External+traffic
> Separation of Internal and External traffic
> -------------------------------------------
>
> Key: KAFKA-4565
> URL: https://issues.apache.org/jira/browse/KAFKA-4565
> Project: Kafka
> Issue Type: Bug
> Reporter: Ismael Juma
> Assignee: Ismael Juma
>
> During the 0.9.0.0 release cycle, support for multiple listeners per broker
> was introduced (KAFKA-1809). Each listener is associated with a security
> protocol, ip/host and port. When combined with the advertised listeners
> mechanism, there is a fair amount of flexibility with one limitation: at most
> one listener per security protocol in each of the two configs (listeners and
> advertised.listeners).
> In some environments, one may want to differentiate between external clients,
> internal clients and replication traffic independently of the security
> protocol for cost, performance and security reasons. See the KIP for more
> details:
> https://cwiki.apache.org/confluence/display/KAFKA/KIP-103%3A+Separation+of+Internal+and+External+traffic
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
