[
https://issues.apache.org/jira/browse/STORM-2421?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15989719#comment-15989719
]
Mal Graty commented on STORM-2421:
----------------------------------
Ooops! Reading it back I can see how you would have gotten that impression. I
was just grabbing names from
[DaemonConfig.java|https://github.com/apache/storm/blob/a4afacd9617d620f50cf026fc599821f7ac25c79/storm-server/src/main/java/org/apache/storm/DaemonConfig.java#L146]
I didn't notice until now how like environment variables they appear without
proper context! D:
> Support lists of childopts beyond just worker
> ---------------------------------------------
>
> Key: STORM-2421
> URL: https://issues.apache.org/jira/browse/STORM-2421
> Project: Apache Storm
> Issue Type: Improvement
> Components: storm-core
> Affects Versions: 1.0.2
> Reporter: Mal Graty
> Priority: Minor
> Time Spent: 50m
> Remaining Estimate: 0h
>
> The following worker childopts configuration options all support both a
> string value and a list of strings value:
> {code}
> WORKER_CHILDOPTS
> WORKER_PROFILER_CHILDOPTS
> WORKER_GC_CHILDOPTS
> TOPOLOGY_WORKER_CHILDOPTS
> TOPOLOGY_WORKER_GC_CHILDOPTS
> TOPOLOGY_WORKER_LOGWRITER_CHILDOPTS
> {code}
> Currently the following childopts configuration options only support strings:
> {code}
> NIMBUS_CHILDOPTS
> LOGVIEWER_CHILDOPTS
> UI_CHILDOPTS
> PACEMAKER_CHILDOPTS
> DRPC_CHILDOPTS
> SUPERVISOR_CHILDOPTS
> {code}
> Please could lists be supported across all childopts options as it makes
> configuration management and building easier using automated tools such as
> Chef and Puppet.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
