[
https://issues.apache.org/jira/browse/SLIDER-685?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14298569#comment-14298569
]
Steve Loughran commented on SLIDER-685:
---------------------------------------
# there's already {{slider-server.xml}}; I've created an empty sample one
# I think we could supplement that with something in appconf.xml for AM
options; something like
{code}
sysprop.key : value
config.configopt: value
{code}
With generic names like this we could (in future) have them picked up by other
services
> Better propagation of config options from client to deployed service
> --------------------------------------------------------------------
>
> Key: SLIDER-685
> URL: https://issues.apache.org/jira/browse/SLIDER-685
> Project: Slider
> Issue Type: Improvement
> Components: appmaster, client
> Affects Versions: Slider 0.60
> Reporter: Steve Loughran
> Fix For: Slider 2.0.0
>
>
> We are only propagating a few specific options from the slider client to the
> AM: FS binding, non-HA RM binding, registry binding.
> This makes it hard to set server-side properties such as metrics options
> I propose that we propagate all options from slider-client.xml, leaving all
> that are pulled in indirectly from the -site.xml files alone. Also: include
> all properties set on the command line with {{-D key=value}}. As these are
> picked up before the client is instantiated, we'll need to rummage into the
> Configuration and filter values based on their provenance.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
