question Re: execution of pig script using Oozie, job always in running state only in Archives of Support Questions (Read Only)

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

nejmhadjmbarek — Sun, 18 Aug 2019 11:22:23 GMT

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

pig.pig script

worklow.xml

job.properties

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

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

KuldeepK — Tue, 24 May 2016 21:01:01 GMT

@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.

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

nejmhadjmbarek — Sun, 18 Aug 2019 11:21:53 GMT

@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

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

KuldeepK — Sun, 18 Aug 2019 11:21:40 GMT

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

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

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

jyadav — Tue, 24 May 2016 22:35:29 GMT

@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.

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

nejmhadjmbarek — Sun, 18 Aug 2019 11:21:31 GMT

@Kuldeep Kulkarni

there is 2 node active and 1 node unhealthy

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

KuldeepK — Tue, 24 May 2016 23:56:41 GMT

@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 🙂 )

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

nejmhadjmbarek — Wed, 25 May 2016 16:04:14 GMT

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