[jira] [Commented] (KAFKA-8792) Default ZK configuration to disable AdminServer

2019-08-12 Thread ASF GitHub Bot (JIRA)


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

ASF GitHub Bot commented on KAFKA-8792:
---

gwenshap commented on pull request #7203: KAFKA-8792; Default ZK configuration 
to disable AdminServer
URL: https://github.com/apache/kafka/pull/7203
 
 
   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.
   
   ### Committer Checklist (excluded from commit message)
   - [ ] Verify design and implementation 
   - [ ] Verify test coverage and CI build status
   - [ ] Verify documentation (including upgrade notes)
   
 

This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


> 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)


[jira] [Commented] (KAFKA-8792) Default ZK configuration to disable AdminServer

2019-08-12 Thread JIRA


[ 
https://issues.apache.org/jira/browse/KAFKA-8792?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=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)