[
https://issues.apache.org/jira/browse/FALCON-141?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15051231#comment-15051231
]
Srikanth Sundarrajan commented on FALCON-141:
---------------------------------------------
Instead of storing state with each entity that needs update, I would like you
to consider the alternative of staging the cluster update and attempting
repeatedly till all the affected entities are updated. This will help avoid
maintaining state at each dependent entity level.
Also one other
[scenario|https://issues.apache.org/jira/browse/FALCON-141?focusedCommentId=15030357&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-15030357]
I wanted to bring to your attention: (particularly relating to NN related
changes)
Consider the case where NN is migrated and oozie is started up, it has to
remain in safe mode, else it will keep launching instances as per older
definition & failing. But while in safe mode, cluster entity itself can't be
updated. Now if we remove oozie from safe mode and allow older instances to
fail, you might have a bit of cleaning up to do (re-runs, that I was referring
to in my earlier comment)
> Support cluster updates
> -----------------------
>
> Key: FALCON-141
> URL: https://issues.apache.org/jira/browse/FALCON-141
> Project: Falcon
> Issue Type: Bug
> Reporter: Shwetha G S
> Assignee: Balu Vellanki
>
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
