Virag Kothari created OOZIE-1272:
------------------------------------
Summary: Two workflow jobs mapped to a single coordinator action
Key: OOZIE-1272
URL: https://issues.apache.org/jira/browse/OOZIE-1272
Project: Oozie
Issue Type: Bug
Reporter: Virag Kothari
Fix For: trunk
CoordinatorActionstart is being called multiple times for same action id for
two different workflows as seen below
{code}
2013-03-18 19:39:41,815 DEBUG CoordActionStartXCommand:545 - USER[-] GROUP[-]
TOKEN[-] APP[-] JOB[0000057-130318185730776-oozie-oozi-C]
ACTION[0000057-130318185730776-oozie-oozi-C@1] Updating WF record for WFID
:0000471-130318185730776-oozie-oozi-W with parent id:
0000057-130318185730776-oozie-oozi-C@1
2013-03-18 19:39:49,618 DEBUG CoordActionStartXCommand:545 - USER[-] GROUP[-]
TOKEN[-] APP[-] JOB[0000057-130318185730776-oozie-oozi-C]
ACTION[0000057-130318185730776-oozie-oozi-C@1] Updating WF record for WFID
:0000473-130318185730776-oozie-oozi-W with parent id:
0000057-130318185730776-oozie-oozi-C@1
{code}
loadState() implementation is blank which makes the verifyPrecondition() check
the coordinator action loaded in eagerLoadState(). So the coordinator action
might be stale as it was loaded without a lock.
LoadState() should be made to call eagerLoadState() similar to other XCommands.
Another issue is getKey() is not overridden so Multiple Coordactionstart for a
given action are not removed as duplicates
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
