Question

I have a problem with running oozie coordinator jobs. Below is my job properties and xml file codes. While submitting the job there was no errors, but the job is always in 'PREP' state. I have to manually kill the job after some extent of waiting. When executing the workflow job separately, it was completed successfully.

Can you please let me know what could be wrong in my co-ord job?

Here is my coordinator.xml

coordinator.xml

Here is my coordinatorjob.properties

coordinatorjob.properties

Thanks,

Kalai

Was it helpful?

Solution

Coordinator is in status PREP when it's start time is in the future. Start time in your config is 2014-02-25 11:31 UTC, so if you submitted in at the time of posting the question (2014-02-25 06:45 UTC) it still had about 5 hours to wait in PREP status before creating the first materialization and switching to RUNNING. See documentation about status transitions.

OTHER TIPS

Synchronous jobs (individual jobs, not coordinator jobs, etc.) do the actual work while being in PREP state. It's the case of the SSH Action for example (even though there it is a little more complicated because the java code happens synchronously but the remote shell script is executed asynchronously).

In your case, I think Dmitry's answer is the more helpful one, but it's good to keep in mind that there can be other reasons for being in the PREP state too.

Licensed under: CC-BY-SA with attribution
Not affiliated with StackOverflow
scroll top