[
https://issues.apache.org/jira/browse/AMBARI-17241?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15373482#comment-15373482
]
Siddharth Wagle commented on AMBARI-17241:
------------------------------------------
[~arpitagarwal] has a valid concern, apply configs without restart would
invariably mean triggering some custom command for the service to pick up the
new config changes. The scope of this feature should include the hooks for
specifying what command to run in order to refresh configs for a service before
returning success.
+1 [~tctruong213] suggestion for calling the tag "require-restart", which is
implicitly true by default. \
*Note*: The API /stacks, endpoint should support querying of configs that do
not require restart
> 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)
