The SSH connection is established initially at the beginning of the action and the <command> tag executes the command passed within the tags, but it takes a while(~ around 3 hours) for the command to execute, and in the meantime this action gets updated to COMPLETED and proceeds on to the next subsequent action, whereas former command is still in execution phase.   This exception arises when Oozie starts on the latter SSH action while the prior SSH action is still in execution.   So why does Oozie presumes the prior SSH action as completed yet the command is still in process? ... View more