[
https://issues.apache.org/jira/browse/OOZIE-1807?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14035662#comment-14035662
]
Rohini Palaniswamy commented on OOZIE-1807:
-------------------------------------------
[~shwethags],
This takes the chmod command (or other filesystem commands like cp,mv,chgrp,
etc) approach. It attempts on all the coordinators and reports all the failed
ones in the error message. Behaviour is same as before without this change, but
all the errors get reported now to the user. If you want an atomic option we
can open a separate jira as it is a lot more work.
> 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)
