[
https://issues.apache.org/jira/browse/STORM-1056?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15209115#comment-15209115
]
Erik Weathers commented on STORM-1056:
--------------------------------------
[~kabhwan]: ahh, seems that [the release notes for storm
0.10.0|https://storm.apache.org/2015/11/05/storm0100-released.html] were just
missing STORM-1056, but it's actually present in v0.10.0:
* https://github.com/apache/storm/blob/v0.10.0/bin/storm.py#L80
And in the binary release tarball:
{code}
(/tmp) % wget
http://www.carfab.com/apachesoftware/storm/apache-storm-0.10.0/apache-storm-0.10.0.tar.gz
...
(/tmp) % tar -xf apache-storm-0.10.0.tar.gz
(/tmp/apache-storm-0.10.0) % grep SUPERVI bin/storm.py
STORM_SUPERVISOR_LOG_FILE = os.getenv('STORM_SUPERVISOR_LOG_FILE',
"supervisor.log")
"-Dlogfile.name=" + STORM_SUPERVISOR_LOG_FILE,
{code}
> allow supervisor log filename to be configurable via ENV variable
> -----------------------------------------------------------------
>
> Key: STORM-1056
> URL: https://issues.apache.org/jira/browse/STORM-1056
> Project: Apache Storm
> Issue Type: Task
> Components: storm-core
> Reporter: Erik Weathers
> Assignee: Erik Weathers
> Priority: Minor
> Fix For: 0.9.6
>
>
> *Requested feature:* allow configuring the supervisor's log filename when
> launching it via an ENV variable.
> *Motivation:* The storm-on-mesos project (https://github.com/mesos/storm)
> relies on multiple Storm Supervisor processes per worker host, where each
> Supervisor is dedicated to a particular topology. This is part of the
> framework's functionality of separating topologies from each other. i.e.,
> storm-on-mesos is a multi-tenant system. But before the change requested in
> this issue, the logs from all supervisors on a worker host will be written
> into a supervisor log with a single name of supervisor.log. If all logs are
> written to a common location on the mesos host, then all logs go to the same
> log file. Instead it would be desirable to separate the supervisor logs
> per-topology, so that each tenant/topology-owner can peruse the logs that are
> related to their own topology. Thus this ticket is requesting the ability to
> configure the supervisor log via an environment variable whilst invoking
> bin/storm.py (or bin/storm in pre-0.10 storm releases).
> When this ticket is fixed, we will include the topology ID into the
> supervisor log filename for storm-on-mesos.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
