question Oozie > HiveActionExecutor > LauncherMapper died, check Hadoop LOG for job in Support Questions

Oozie > HiveActionExecutor > LauncherMapper died, check Hadoop LOG for job

dineshc — Thu, 16 Mar 2017 03:26:25 GMT

An oozie sub-workflow is failing with message as "LauncherMapper died, check Hadoop LOG for job"

On subsequent attempt, the workflow completes successfully.

Various oozie jobs are failing randomly at any sub-workflow and work fine on subsequent attempt.

I tried checking hadoop logs but when the failure happens there are no mapred or yarn logs for that job/application.

Any hints are highly appreciated.

Re: Oozie > HiveActionExecutor > LauncherMapper died, check Hadoop LOG for job

aervits — Thu, 16 Mar 2017 05:33:15 GMT

Please check whether failures only occur on the exact same node? Also can you drill down into the yarn job logs and see what error you get?

Re: Oozie > HiveActionExecutor > LauncherMapper died, check Hadoop LOG for job

dineshc — Thu, 16 Mar 2017 10:53:11 GMT

@Artem Ervits - different workflows failed on different nodes, however, their re-attempt were on the same node as their first attempt.

also the yarn logs do not exist for the failed/killed ones, i mean, i tried > yarn logs -applicationId <failedAppId> but it said the logs do not exist.

In order to verify the command i tried to get logs for a successful one and was able to get logs.

Thank you.

Re: Oozie > HiveActionExecutor > LauncherMapper died, check Hadoop LOG for job

sreeviswa_athic — Wed, 22 Mar 2017 01:56:39 GMT

Restart yarn & oozie services and then try to run your oozie workflow again. I had a similar situation and I tried many things, in the end the restart solved the problem for me.

Re: Oozie > HiveActionExecutor > LauncherMapper died, check Hadoop LOG for job

dineshc — Wed, 22 Mar 2017 02:06:07 GMT

It is weird but a restart indeed solved the issue. Wondering what the root cause could be. If you have any luck arriving at the root cause, please share here in future. 🙂