[
https://issues.apache.org/jira/browse/AMBARI-17241?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15357780#comment-15357780
]
Tuong Truong commented on AMBARI-17241:
---------------------------------------
[~mithmatt] Thanks for demoing this at the Friday's meeting. I think it's a
important operational performance feature. I just read thru the design and
have some input:
1. In term of tagging the configuration, I think it would be more general if
we support the attribute "require-restart" instead e.g.
<require-restart>false</require-restart> and "true" will be the default to
preserve existing semantic.
2. "reload" is ambiguous in a more generic context. Instead, it may be better
to introduce a new explicit action like: "Apply configuration Change" which
may trigger a server restart if the config changes require a service restart.
If not, then the service will do whatever needed to apply the configuration
change.
3. AMBARI-17401 is working on supporting additional attribute for custom
configuration. This should fold nicely into it for more general support of
properties.
> Services should be able to reload configs without requiring restart
> -------------------------------------------------------------------
>
> Key: AMBARI-17241
> URL: https://issues.apache.org/jira/browse/AMBARI-17241
> Project: Ambari
> Issue Type: New Feature
> Reporter: Matt
> Assignee: Matt
> Priority: Minor
> Fix For: trunk
>
> Attachments: AMBARI-17241-Design-Proposal.pdf
>
>
> The current implementation forces users to restart the service if any of the
> configurations have been updated.
> However some of the services support reloading the configuration parameters
> during run-time which does not require restart of the service.
> This behavior should be driven by metadata defined in configuration files.
> {code}
> <property>
> <name>foo-bar</name>
> <value>0</value>
> <supports-reload>true</supports-reload>
> </property>
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
