[jira] [Commented] (KAFKA-4565) Separation of Internal and External traffic (KIP-103)

["Jurriaan Pruis (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/KAFKA-4565?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16032616#comment-16032616 ] 

Jurriaan Pruis commented on KAFKA-4565:
---------------------------------------

This KIP mentions a Kafka setup with a load balancer (i.e. all brokers advertise the same hostname). How would this work in practice? For example Kafka consumers need to connect to multiple brokers in order to consume from partitions across them (also the consumer group needs a specific coordinator to connect to). 

> Separation of Internal and External traffic (KIP-103)
> -----------------------------------------------------
>
>                 Key: KAFKA-4565
>                 URL: https://issues.apache.org/jira/browse/KAFKA-4565
>             Project: Kafka
>          Issue Type: Bug
>            Reporter: Ismael Juma
>            Assignee: Ismael Juma
>              Labels: kip
>             Fix For: 0.10.2.0
>
>
> 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.15#6346)