[
https://issues.apache.org/jira/browse/STORM-248?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14253722#comment-14253722
]
ASF GitHub Bot commented on STORM-248:
--------------------------------------
GitHub user fmazoyer opened a pull request:
https://github.com/apache/storm/pull/353
STORM-248 STORM-322 proposal for fix
Details are in JIRA https://issues.apache.org/jira/browse/STORM-248.
As a collateral benefit, this also addresses JIRA
https://issues.apache.org/jira/browse/STORM-322.
Could you please review ?
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/fmazoyer/storm STORM-248
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/storm/pull/353.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #353
----
commit b2f8eb651d3e8dbd7939aae126d803da6b948663
Author: fmazoyer <frantz.mazo...@altran.com>
Date: 2014-12-19T16:12:57Z
STORM-248 STORM-322 proposal for fix
----
> cluster.xml location is hardcoded for workers.
> ----------------------------------------------
>
> Key: STORM-248
> URL: https://issues.apache.org/jira/browse/STORM-248
> Project: Apache Storm
> Issue Type: Bug
> Reporter: Edward Goslin
> Assignee: Frantz Mazoyer
> Priority: Trivial
>
> when the supervisor spawns a worker process, it assumes the cluster.xml is in
> -Dlogback.configurationFile=" storm-home "/logback/cluster.xml"
> It should take the VM arguement for the supervisor and pass it down to the
> worker.
> System.get("logback.configurationFile", storm-home + "/logback/cluster.xml)
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
