I've been truing to run Oozie job for one of examples from doc/examples/apps/map-reduce just to be sure my cluster installation is fine but see all my oozie jobs hovering in PREP state.
Use 8020 port for NameNode
and 8050 for jobTracker
and the command to kick a job is :
oozie job -oozie http://#######:11000/oozie/ -config ./job.properties -run
I've been truing to do this both under ambari-qa and root user but result is negative.
At the same time, I can see the same task has finished successfully onse during HW installation somehow :
I fill like I screwed sonthing out or missed somthing.
My question here what the correct way to run Ooozie job ?
@roman bubon Command used to run oozie job is correct. Is it possible for you to share the oozie.log to analyze why oozie jobs are in prep state. Is sufficient slots capacity are available to run the oozie job, please confirm. Also mention what is the version of HDP used.
@roman bubon Shared Oozie logs are not of duration when Oozie job executed. Can you please provide all the oozie.log from Oozie server log folder.
For slots availability, you can view on ResourceManager UI.