Support Questions
Find answers, ask questions, and share your expertise

What happens to the Oozie launcher job when Oozie shuts down and restarts?

New Contributor

I've been playing around testing Oozie restartability and noticed that if I turn Oozie off during a running workflow action and then turn Oozie back on after the action has completed, the workflow hangs/delays for 10 minutes until it moves onto the next action. I'm wondering if this has to do with the launcher job for the action not knowing how to return the job status while Oozie was down. Does the launcher job stay alive when Oozie shuts down? What does it do when Oozie comes back up, and what causes the 10 minute delay?