You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jira@kafka.apache.org by "Sönke Liebau (JIRA)" <ji...@apache.org> on 2019/08/13 05:14:00 UTC
[jira] [Commented] (KAFKA-8792) Default ZK configuration to disable
AdminServer
[ https://issues.apache.org/jira/browse/KAFKA-8792?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16905827#comment-16905827 ]
Sönke Liebau commented on KAFKA-8792:
-------------------------------------
I agree, port 8080 tends to be one of the first ports software binds to for some reason, so there is a reasonable chance that people wo test locally will have something running on that port.
> Default ZK configuration to disable AdminServer
> -----------------------------------------------
>
> Key: KAFKA-8792
> URL: https://issues.apache.org/jira/browse/KAFKA-8792
> Project: Kafka
> Issue Type: Improvement
> Reporter: Gwen Shapira
> Priority: Major
>
> Kafka ships with default ZK configuration. With the upgrade to ZK 3.5, our defaults include running ZK's AdminServer on port 8080. This is an unfortunate default as it tends to cause conflicts.
> I suggest we default to disable ZK's AdminServer in the default ZK configs that we ship. Users who want to use AdminServer can enable it and set the port to something that works for them. Realistically, in most production environments, a different ZK server will be used anyway. So this is mostly to save new users who are trying Kafka on their own machine from running into accidental and frustrating port conflicts.
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)