[
https://issues.apache.org/jira/browse/OOZIE-1807?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14034328#comment-14034328
]
Purshotam Shah commented on OOZIE-1807:
---------------------------------------
Yes, it make sense.
We might have to do when we fix OOZIE-1863.
While submitting bundle if any of coord submit has failed, we should rollback
the whole transaction.
In current scenario we queue all coord jobs and if any one failed,
StatusTransitService service kills submitted coord jobs and bundle.
For change command, bundle and coord doesn't need to be in same transition.
If change command on any coord fails, we ignore and report it.
> Make bundle change command synchronous
> --------------------------------------
>
> Key: OOZIE-1807
> URL: https://issues.apache.org/jira/browse/OOZIE-1807
> Project: Oozie
> Issue Type: Bug
> Reporter: Ryota Egashira
> Assignee: Purshotam Shah
> Attachments: OOZIE-1807-V2.patch, OOZIE-1807-V3.patch,
> OOZIE-1807.patch
>
>
> It confusion for user when they issue change command and they are not sure if
> changes are applied to all coords jobs.
> Fix is to call synchronously all coord from bundle and display error message
> (if any) to user.
> purushah$
> /Users/purushah/views/sysc_command/oozie/distro/target/oozie-4.1.0-SNAPSHOT-distro/oozie-4.1.0-SNAPSHOT/bin/oozie
> job -change 0000002-140424165425407-oozie-puru-B -value
> endtime=2013-01-01T00:00Z -oozie http://localhost:11000/oozie
> Change command for coord job : 0000004-140424165425407-oozie-puru-C failed.
> Reason : Coord is in killed state
> Change command for coord job : 0000003-140424165425407-oozie-puru-C failed.
> Reason : Coord is in killed state
> purushah$
--
This message was sent by Atlassian JIRA
(v6.2#6252)
