You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@oozie.apache.org by "Jaydeep Vishwakarma (JIRA)" <ji...@apache.org> on 2015/07/14 08:14:04 UTC

[jira] [Commented] (OOZIE-2302) Reload feature for oozie-site config

    [ https://issues.apache.org/jira/browse/OOZIE-2302?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14625893#comment-14625893 ] 

Jaydeep Vishwakarma commented on OOZIE-2302:
--------------------------------------------

Reload for all properties are not the good idea, Some properties like DB information or Services cannot be the candidate reload config. oozie-site config should be divided in two parts. One will be same as oozie-site.xml (for backward compatibility ) and another would be oozie-props-site.xml.  Reload of will be possible through admin command.
oozie-dev, Please share your thoughts.

> 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)