About gaurab_dawn

gkeys · ‎09-21-2016

Syncsort is a 3rd party partner of ours. We work very closely with them but we do not support them. I suggest you head over to their support site http://bigdatakb.syncsort.com/Default.htm#KB/FAQ/297_Creating_DMX-h_Job_Tutorial.htm

gaurab_dawn · ‎09-14-2016

Thanks @mqureshi , It was indeed a queue issue. I have earlier configured capacity scheduler giving where both the datanodes are associated with one queue which I wasn't using while submitting this job. Once I removed that configuration, job is running just fine. Many thanks for your advice.

sudarshankumar_ · ‎03-09-2017

Hi me too getting the same error .i Did kinit but still exception persist.

gaurab_dawn · ‎09-13-2016

Thanks, checking the log was helpfull. But restarting the Yarn RM resolved the issue.

vranganathan · ‎09-08-2016

Why would you restart the RM for this?

gaurab_dawn · ‎08-18-2016

Hi Murali, you are right. Script was executing but output wasn't matching with the below action. ${wf:actionData('shell-node')['my_output'] eq 'Hello'} Now, I have changed the shell script as below and oozie job has finished successfully. >> echo "my_output=Hello" Thanks.

gaurab_dawn · ‎09-13-2016

Thanks, It was really helpful

gaurab_dawn · ‎09-13-2016

we were using Hadoop 2.7.1.2.4.2.0-258

Online	Offline
Last Visited	‎10-12-2016 08:51 AM

Member Since	‎07-26-2016 01:29 PM
Last Visited	‎10-12-2016 08:51 AM
Posts	36
Kudos received	8

Cloudera Community

Re: yarn is not listing all the nodes in the clust...

Re: Oozie sqoop action Error

Re: ETL Tool using Yarn Distributed Shell jar

Re: Sqoop jobs are not running

Re: Failed to find any Kerberos tgt Error

Re: yarn is not listing all the nodes in the clust...

Re: Oozie sqoop action Error

Re: Oozie job is getting killed

Re: Trying to create two node labels "x" as exclus...

Re: How to configure multiple node labels in one n...