You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jira@kafka.apache.org by "Mickael Maison (Jira)" <ji...@apache.org> on 2023/04/13 10:47:00 UTC

[jira] [Commented] (KAFKA-13299) Accept listeners that have the same port but use IPv4 vs IPv6

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

Mickael Maison commented on KAFKA-13299:
----------------------------------------

Moving to 3.6.0 since we are past code freeze for 3.5.0

> Accept listeners that have the same port but use IPv4 vs IPv6
> -------------------------------------------------------------
>
>                 Key: KAFKA-13299
>                 URL: https://issues.apache.org/jira/browse/KAFKA-13299
>             Project: Kafka
>          Issue Type: Improvement
>            Reporter: Matthew de Detrich
>            Assignee: Matthew de Detrich
>            Priority: Major
>             Fix For: 3.6.0
>
>
> Currently we are going through a process where we want to migrate Kafka brokers from IPv4 to IPv6. The simplest way for us to do this would be to allow Kafka to have 2 listeners of the same port however one listener has an IPv4 address allocated and another listener has an IPv6 address allocated.
> Currently this is not possible in Kafka because it validates that all of the listeners have a unique port. With some rudimentary testing if this validation is removed (so we are able to have 2 listeners of the same port but with different IP versions) there doesn't seem to be any immediate problems, the kafka clusters works without any problems.
> Is there some fundamental reason behind this limitation of having unique ports? Consequently would there be any problems in loosening this limitation (i.e. duplicate ports are allowed if the IP versions are different) or just altogether removing the restriction 



--
This message was sent by Atlassian Jira
(v8.20.10#820010)