You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@kafka.apache.org by "ASF GitHub Bot (JIRA)" <ji...@apache.org> on 2017/01/12 14:13:52 UTC
[jira] [Commented] (KAFKA-4565) Separation of Internal and External
traffic (KIP-103)
[ https://issues.apache.org/jira/browse/KAFKA-4565?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15821082#comment-15821082 ]
ASF GitHub Bot commented on KAFKA-4565:
---------------------------------------
GitHub user ijuma opened a pull request:
https://github.com/apache/kafka/pull/2354
KAFKA-4565: Separation of Internal and External traffic (KIP-103)
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/ijuma/kafka kafka-4565-separation-of-internal-and-external-traffic
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/kafka/pull/2354.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #2354
----
commit 8c5dc93e2ccea2c4c65e6ce28f22adf0dd9c6be8
Author: Ismael Juma <is...@juma.me.uk>
Date: 2017-01-12T14:11:20Z
KAFKA-4565: Separation of Internal and External traffic (KIP-103)
----
> 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.4#6332)