[
https://issues.apache.org/jira/browse/OOZIE-2302?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14626031#comment-14626031
]
Srikanth Sundarrajan commented on OOZIE-2302:
---------------------------------------------
Consider separating the conf into static startup config and a dynamic runtime
config. This however is backward incompatible and would require a general
consensus or a way to keep it compatible, till user chooses to separate them.
> Reload feature for oozie-site config
> -------------------------------------
>
> Key: OOZIE-2302
> URL: https://issues.apache.org/jira/browse/OOZIE-2302
> Project: Oozie
> Issue Type: New Feature
> Components: core
> Reporter: Jaydeep Vishwakarma
> Assignee: Jaydeep Vishwakarma
>
> Whenever user wants to add/modify any property, He has to restart the oozie
> server to see the impact of config updates. It is very inconvenient as User
> has to either kill or drain out all the jobs from oozie, which eventually
> lead to slow down the production pace. We should suppose to have reload
> support for config updates.
>
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
