[jira] [Commented] (KAFKA-1234) All kafka-run-class.sh to source in user config file (to set env vars like KAFKA_OPTS)

["Benjamin Black (JIRA)" <ji...@apache.org>]

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

Benjamin Black commented on KAFKA-1234:
---------------------------------------

There are OS-specific ways of doing this that would be preferred if we are talking about binary packages. For example, on Ubuntu the standard way to do this is with a file in /etc/default. 

> All kafka-run-class.sh to source in user config file (to set env vars like KAFKA_OPTS)
> --------------------------------------------------------------------------------------
>
>                 Key: KAFKA-1234
>                 URL: https://issues.apache.org/jira/browse/KAFKA-1234
>             Project: Kafka
>          Issue Type: Improvement
>          Components: config
>    Affects Versions: 0.8.0
>            Reporter: Alex Gray
>            Priority: Trivial
>         Attachments: patch.txt
>
>
> We are using the distributed version of kafka:
> http://apache.mirrors.lucidnetworks.net/kafka/0.8.0/kafka_2.8.0-0.8.0.tar.gz
> And we would like to set some environment variables, particularly KAFKA_OPTS when the kafka service starts.
> In other words, when someone does a "sudo service kafka start" we would like to set some environment variables.
> We cannot do this *without* modifying either /etc/init.d/kafka or bin/kafka-run-class.sh, and we don't want to modify files that we don't own.
> The solution is to have kafka source in a user specific file that may have these environment variables set.
> I'm attaching the patch file to show you what I mean.



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)