[
https://issues.apache.org/jira/browse/AMBARI-17241?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15371840#comment-15371840
]
Arpit Agarwal commented on AMBARI-17241:
----------------------------------------
Hi [~mithmatt] I like the idea of Ambari supporting restart-less configuration
changes.
This may be a naive question but how will Ambari communicate the configuration
change to the service when restart is not required? I missed that from a quick
look at the doc.
Also is the supports-reload or restart-required parameter expected to be
configured by the administrator? That could be error prone.
> 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)
