You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@slider.apache.org by "Steve Loughran (JIRA)" <ji...@apache.org> on 2014/11/26 14:28:12 UTC
[jira] [Created] (SLIDER-685) Better propagation of config options
from client to deployed service
Steve Loughran created SLIDER-685:
-------------------------------------
Summary: 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 0.70
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)