[
https://issues.apache.org/jira/browse/AMBARI-17241?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Matt updated AMBARI-17241:
--------------------------
Comment: was deleted
(was: Thanks for your suggestions [~tctruong213]
>From your suggestion I infer that you would only show a button to the user
>saying 'Apply Configuration Changes'.
(i) if all configs that were changed does not require restart ... show no
warning, apply changes
(ii) if configs that were changed contains configs requiring restart and
configs not requiring restart ... show warning, restart service
(iii) if all configs that were changed requires restart ... show warning,
restart service
Please confirm if my understanding described above is correct. It would need
only some minor UI changes to the prototype I presented, to make it work that
way.
Just putting my thoughts on scenario (ii) above, where user changes some
configs, which need restart and some which don't.
Would there be a situation where user wants to apply the configurations, which
do not require restart, immediately, without affecting running jobs? And later
restart the service to apply other configs which were not applied before, after
the running jobs have been completed?
This action would apply the configs 'partially' - apply changes which do not
require restart first. From implementation perspective, this would be
challenging to implement - tracking if each config was applied or not is more
complex. Any thoughts on this [~tctruong213] whether users/customers require
this partial way of applying configs? This can also be an enhancement for this
JIRA, if required.)
> 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)
