[
https://issues.apache.org/jira/browse/STORM-248?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14223116#comment-14223116
]
Frantz Mazoyer commented on STORM-248:
--------------------------------------
Hello,
I would like to lift this limitation to ease my deployments.
Here's the fix I propose:
In file supervisor.clj, function launch-worker, in the 'let', I would add
'storm-log-conf-file' like so:
...
(let [conf (:conf supervisor)
storm-home (System/getProperty "storm.home")
...
storm-log-conf-file (or (System/getProperty
"logback.configurationFile") (str storm-home file-path-separator "logback"
file-path-separator "cluster.xml"))
...
and substitute current concatenation of logback.configurationFile with it:
...
(str "-Dlogback.configurationFile=" storm-log-conf-file)
...
If it's ok with you, can I submit a pull request on the master, next?
Thanks a lot for your help
> 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)
