[
https://issues.apache.org/jira/browse/AMBARI-17241?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15374525#comment-15374525
]
Matt commented on AMBARI-17241:
-------------------------------
[~swagle] [~arpitagarwal]
Considering that each service component might have its own way to refresh its
configs (similar to how each component has start and stop), in my prototype I
made RELOAD a command similar to CONFIGURE, START or STOP that is recognized by
the REST API and runs the reload method on each host component.
Code snippet from
ambari-server/src/main/java/org/apache/ambari/server/metadata/ActionMetadata.java:
{code}
private void fillHostComponentCommands() {
//Standart commands for any host component
defaultHostComponentCommands.add("RESTART");
defaultHostComponentCommands.add("START");
...
defaultHostComponentCommands.add("RELOAD");
defaultHostComponentCommands.add("CONFIGURE");
...
}
{code}
Code snippet from
ambari-common/src/main/python/resource_management/libraries/script/script.py:
{code}
def reload(self, env):
"""
To be overridden by subclasses
"""
pass
{code}
[~swagle] Having an endpoint which would support querying configs which do not
require restart, is nice :) - something that I never thought about. Is there a
specific use case that you have in mind, where this would be beneficial?
> 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)