[
https://issues.apache.org/jira/browse/OOZIE-1791?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13966586#comment-13966586
]
Rohini Palaniswamy commented on OOZIE-1791:
-------------------------------------------
[~egashira],
Can you correct the title and description? It does not remove the
coordinator from the bundle. Just changes the status to IGNORED of a terminated
coordinator.
> add IGNORED status to Coordinator to allow removing Coord job from Bundle in
> runtime
> ------------------------------------------------------------------------------------
>
> Key: OOZIE-1791
> URL: https://issues.apache.org/jira/browse/OOZIE-1791
> Project: Oozie
> Issue Type: Bug
> Reporter: Ryota Egashira
>
> data pipeline customers need clean way to remove coord job from bundle job in
> runtime.
> currently to make a change to coordinator after bundle submission, it is
> required to relaunch entire bundle after fixing coord xml or run another
> bundle with new coord. OOZIE-1769 to support changing coord properties in
> runtime. in many scenarios, customers want to remove the coord from the
> bundle first, and fix the coord, put it back, without stopping entire bundle
> job.
> suggested approach is to add IGNORED status to Coord Job/Actions. once CLI
> command to remove coord job from bundle issued, change status of coord
> job/actions to IGNORED (probably bundle aciton, too). If one of coordinators
> in the bundle has IGNORED status, then the status of the bundle would be
> RUNNING, not RUNNINGWITHERROR. (StatusTransitService need to be changed for
> couple of other cases).
> Only coord job/actions in terminal state (SUSPENDED, KILLED or FAILED) can be
> changed to IGNORED. PREP, RUNNING, WAITING or SUCCEEDED ones cannot be
> changed.
> We'd like to have discussion on this approach before proceed. Any feedback
> appreciated.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
