Support Questions

Find answers, ask questions, and share your expertise

execution of pig script using Oozie, job always in running state only

I need help with oozie, i am trying to run a script pig when i execute Oozie it shows in Running state only, can anyone please help me to identify as if anything wrong with my workflow.xml or jo.properties. I tried validating workflow.xml and it did not show any error.thnx

4478-capture-du-2016-05-24-113931.png

4480-capture-du-2016-05-24-110540.png

pig.pig script

4501-capture-du-2016-05-24-113434.png

worklow.xml

4502-capture-du-2016-05-24-113503.png

job.properties

4479-capture-du-2016-05-24-113523.pngcapture-du-2016-05-24-113523.png(48.2 kB)

1 ACCEPTED SOLUTION

Super Guru

@nejm hadjmbarek

Can you please check status of oozie launcher in Resource Manager UI? Sometimes because of un-availability of NodeManagers your launcher gets stuck in ACCEPTED state and never changes its state to RUNNING and in oozie UI it shows RUNNING.

View solution in original post

7 REPLIES 7

Super Guru

@nejm hadjmbarek

Can you please check status of oozie launcher in Resource Manager UI? Sometimes because of un-availability of NodeManagers your launcher gets stuck in ACCEPTED state and never changes its state to RUNNING and in oozie UI it shows RUNNING.

@Kuldeep Kulkarni

i get accepted : wiating for AM container to be allocated , i don't know what this mean exactly , have you any idea ?? i try to change the configuration in yarn-site.xml but i still get the same status for oozie workflow

4504-capture-du-2016-05-24-171752.png

4503-capture-du-2016-05-24-164318.png

Super Guru

@nejm hadjmbarek - Can you please check if your nodemanagers are healthy?

Please refer below screenshot ( Please look at Active Nodes count )

4493-screen-shot-2016-05-24-at-85957-pm.png

@Kuldeep Kulkarni

there is 2 node active and 1 node unhealthy

4505-capture-du-2016-05-24-180810.png

Super Guru

@nejm hadjmbarek - You already have 6 containers running and 100% memory is utilized (2GB out of 2GB) hence Oozie launcher is unable to get resources. Can you please click on 1 unhealthy node (click on 1) and see what is the issue, if you get that node back then you will have more capacity.

Also,

Please check running applications, you can kill them if they are stuck or not important! ( Please kill them at your own risk, if those jobs are important then please do not kill 🙂 )

i fix the unhealthy node by reducing the memory of this node , after that i run the workflow oozie and it succeed.

@nejm hadjmbarek

Either your cluster doesn't have resources to run the AM container of that oozie job or nodemager is not available or you might have some resource queue settings which restricting the resources.