ambari-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Tuong Truong (JIRA)" <>
Subject [jira] [Commented] (AMBARI-17241) Services should be able to reload configs without requiring restart
Date Tue, 05 Jul 2016 16:25:11 GMT


Tuong Truong commented on AMBARI-17241:

[~mithmatt] yes, that is what I have in mind.  in (ii),(iii) above, show warning/confirmation
so that users can opt out if they are not ready to restart.

In the case there is a mixture of config type are changed in the same config change save,
I think we should stick to strict transaction semantics of whether the config changes did
get applied or not, and should not allow ambiguity; otherwise, it can be problematic when
trying to debug config changes that caused some issues as to which config changes was pickup
and which was not.   

One potential issue is that we need to aggregate the restart/no-restart state across multiple
config save to ensure proper state it maintained.

> Services should be able to reload configs without requiring restart
> -------------------------------------------------------------------
>                 Key: AMBARI-17241
>                 URL:
>             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

View raw message