You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@kafka.apache.org by "Sriharsha Chintalapani (JIRA)" <ji...@apache.org> on 2015/07/29 16:03:04 UTC
[jira] [Commented] (KAFKA-2383) kafka-env should be separated
between client and server
[ https://issues.apache.org/jira/browse/KAFKA-2383?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14646069#comment-14646069 ]
Sriharsha Chintalapani commented on KAFKA-2383:
-----------------------------------------------
[~AdamWesterman] kafka-env.sh is not merged int apache yet https://issues.apache.org/jira/browse/KAFKA-1566 . You might want to add your comment in there.
> 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)