[
https://issues.apache.org/jira/browse/KAFKA-2383?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14646576#comment-14646576
]
Adam Westerman commented on KAFKA-2383:
---------------------------------------
[~sriharsha] Maybe I should narrow my focus on this issue a little bit. The
problem I have is mentioned above where JMX_PORT is getting picked up by both
the broker and client at runtime, causing an attempted double bind to that
port. Perhaps there should be two env variables for this, like JMX_PORT_BROKER
and JMX_PORT_CLIENT.
> kafka-env should be separated between client and server
> -------------------------------------------------------
>
> Key: KAFKA-2383
> URL: https://issues.apache.org/jira/browse/KAFKA-2383
> Project: Kafka
> Issue Type: Improvement
> Components: config
> Affects Versions: 0.8.2.1
> Environment: HDP 2.2.4.2
> Reporter: Adam Westerman
> Priority: Minor
>
> The environment variables set in the kafka-env template take effect in both
> client and server. One instance in which this causes problems is when
> enabling JMX by setting JMX_PORT in the kafka-env template. The broker will
> start successfully, but then when trying to use a client script such as
> kafka-topics.sh it attempts to rebind to that port, throwing an exception and
> preventing the client script from running.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
