[
https://issues.apache.org/jira/browse/OOZIE-2302?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14626775#comment-14626775
]
Robert Kanter commented on OOZIE-2302:
--------------------------------------
I agree, separating the config into two files is not backwards compatible.
It's also not consistent with how other Hadoop projects work.
{quote}It is very inconvenient as User has to either kill or drain out all the
jobs from oozie{quote}
That's not true. You can restart the Oozie server while jobs are still
running. Hadoop jobs already in progress will continue while the Oozie server
is down (because of the launcher job), and any workflows that are ready to
transition or coordinators that are ready to trigger while the Oozie server is
down will do that when the Oozie server comes back up.
> 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)
