You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@kafka.apache.org by "Colin McCabe (Jira)" <ji...@apache.org> on 2023/05/24 23:02:00 UTC

[jira] [Resolved] (KAFKA-14658) When listening on fixed ports, defer port opening until we're ready

     [ https://issues.apache.org/jira/browse/KAFKA-14658?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Colin McCabe resolved KAFKA-14658.
----------------------------------
    Resolution: Fixed

> When listening on fixed ports, defer port opening until we're ready
> -------------------------------------------------------------------
>
>                 Key: KAFKA-14658
>                 URL: https://issues.apache.org/jira/browse/KAFKA-14658
>             Project: Kafka
>          Issue Type: Bug
>            Reporter: Colin McCabe
>            Assignee: Colin McCabe
>            Priority: Major
>
> When we are listening on fixed ports, we should defer opening ports until we're ready to accept traffic. If we open the broker port too early, it can confuse monitoring and deployment systems. This is a particular concern when in KRaft mode, since in that mode, we create the SocketServer object earlier in the startup process than when in ZK mode.
> The approach taken in this PR is to defer opening the acceptor port until Acceptor.start is called. Note that when we are listening on a random port, we continue to open the port "early," in the SocketServer constructor. The reason for doing this is that there is no other way to find the random port number the kernel has selected. Since random port assignment is not used in production deployments, this should be reasonable.



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