[jira] [Updated] (KAFKA-637) Separate log4j environment variable from KAFKA_OPTS in kafka-run-class.sh

["Jay Kreps (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/KAFKA-637?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jay Kreps updated KAFKA-637:
----------------------------

    Resolution: Fixed
      Assignee: Jay Kreps
        Status: Resolved  (was: Patch Available)

This is sensible. Merged this in with KAFKA-718 which has a few other command line cleanups. Would you mind taking a look at that and let's continue any discussion there.
                
> Separate log4j environment variable from KAFKA_OPTS in kafka-run-class.sh
> -------------------------------------------------------------------------
>
>                 Key: KAFKA-637
>                 URL: https://issues.apache.org/jira/browse/KAFKA-637
>             Project: Kafka
>          Issue Type: Improvement
>    Affects Versions: 0.8.1
>            Reporter: Chris Curtin
>            Assignee: Jay Kreps
>            Priority: Minor
>         Attachments: KAFKA-637.patch
>
>
> The kafka-run-class.sh script has an environment variable for 'KAFKA_OPTS' which defines the log4j configuration file with other system variables.
> By moving the log4j settings into their own variable we can set that configuration file without having to also include the system parameters. This way if the script changes in the next release our management scripts won't have (potentially) unexpected side effects.
> We change the logging configuration file in the test environment so we can run multiple brokers on a single machine for testing. Without this option all the logs for all the brokers get jumbled together.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira