Support Questions
Find answers, ask questions, and share your expertise
Announcements
Alert: Welcome to the Unified Cloudera Community. Former HCC members be sure to read and learn how to activate your account here.

Getting through oozie WARNING: Use "yarn jar" to launch YARN applications

Highlighted

Getting through oozie WARNING: Use "yarn jar" to launch YARN applications

New Contributor

I'm getting different result when we run the below query thru Oozie and local.

From Oozie (Query is placed inside shell):-

Query :- Ideally we should not get WARNING message also because we are using “--silent=true” in the beeline statement .

beeline -n srvc_ima_platform -u 'jdbc:hive2://g4t8346c.houston.hp.com:10000/ea_shared;principal=hive/g4t8346c.houston.hp.com@EAITGKDC.HOUSTON.HP.COM' --showHeader=false --outputformat=tsv2 --showHeader=false --outputformat=tsv2 --silent=true -e “SELECT datediff(current_date,max(current_load_time)) , 'SRC_SYS_DMNSN' FROM ea_fin.SRC_SYS_DMNSN;”

Result:-

WARNING: Use "yarn jar" to launch YARN applications.

3 SRC_SYS_DMNSN

From local :-

Query:-

beeline -n srvc_ima_platform -u 'jdbc:hive2://g4t8346c.houston.hp.com:10000/ea_shared;principal=hive/g4t8346c.houston.hp.com@EAITGKDC.HOUSTON.HP.COM' --showHeader=false --outputformat=tsv2 --showHeader=false --outputformat=tsv2 --silent=true -e “SELECT datediff(current_date,max(current_load_time)) , 'SRC_SYS_DMNSN' FROM ea_fin.SRC_SYS_DMNSN;”

Result:-

3 SRC_SYS_DMNSN


l-c307tmp.png
1 REPLY 1

Re: Getting through oozie WARNING: Use "yarn jar" to launch YARN applications

Expert Contributor

Hi @Angel Mondragon

This is a bit strange, I couldn't replicate it on a fresh HDP cluster.

The warning is triggered by this line of code:

egrep "WARNING.*yarn jar" -B1 /usr/hdp/current/hadoop-client/bin/hadoop.distro 
      if [[ -n "${YARN_OPTS}" ]] || [[ -n "${YARN_CLIENT_OPTS}" ]]; then
        echo "WARNING: Use \"yarn jar\" to launch YARN applications." 1>&2

Which means you (or the scripts) set the YARN_OPTS or YARN_CLIENT_OPTS env variables (maybe a previous command sources some environment variables).

Try to do an echo $YARN_OPTS and echo $YARN_CLIENT_OPTS and if one is set do an unset on it.

You can also replicate this on a local shell by doing export YARN_CLIENT_OPTS=test before the beeline

Don't have an account?
Coming from Hortonworks? Activate your account here