[OOZIE-2394] Oozie can execute command without holding lock

• Type: Bug
• Status: Closed
• Priority: Critical
• Resolution: Fixed
• Fix Version/s: 4.3.0
• Assignee: Purshotam Shah
• Reporter: Purshotam Shah
• Created: 06/Nov/15 17:47
• Updated: 02/Dec/16 21:02
• Resolved: 26/Jan/16 18:44

Description

To speedup job submission ( not the the forked actions) we create workflow actions synchronously. We call ActionStartXCommand from SignalXCommand by setting isSynchronous = true. This will bypass lock acquiring, which is Ok, SignalXCommand will have the job lock.

If there is transient error. Same command is requeued which will have isSynchronous flag set to true.

Requeued command will wake-up and started executing without acquiring lock. If the job submission takes more than 2 min, then we might have issue.

Action recovery is set to 2 min ( default), Recovery service will run and submitted new the command. since the first command didn't acquire any lock. Recovery will be able to run the new command.

We will have two same command running parallely.

All our commands are reentrant, we don't have to have set synchronized flag to run multiple command from same thread.
Because of reentrant, command running in same thread should be able to acquire same lock.

Issue Links

• breaks: OOZIE-2501 ZK reentrant lock doesn't work for few cases