ambari-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Siddharth Wagle (JIRA)" <>
Subject [jira] [Commented] (AMBARI-17241) Services should be able to reload configs without requiring restart
Date Thu, 14 Jul 2016 17:45:20 GMT


Siddharth Wagle commented on AMBARI-17241:

+1 for the command, IMO we should call it "RELOAD_CONFIGS", RELOAD by itself is too broad

The API for stacks already exposes configs which the UI / blueprints use during cluster deploy.
Adding the additional capability of filtering by this flag could be benificial for debugging
etc. Also the implementation of _stale\_configs/requires\_reload\_configs_ flag to find out
what configs do not require restart would reach out to the common piece of code that deals
with statically initializing all stack related information. Thereby the API change and the
stale configs change should converge nicely on this common impl to figure out the two sets
of config items.

> 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