[OOZIE-1272] Two workflow jobs mapped to a single coordinator action

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 4.0.0
• Assignee: Ryota Egashira
• Reporter: Virag Kothari
• Created: 18/Mar/13 22:57
• Updated: 31/Aug/13 00:02
• Resolved: 20/Mar/13 07:39

Description

CoordinatorActionstart is being called multiple times for same action id for two different workflows as seen below

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

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