https://community.cloudera.com/t5/Support-Questions/Yarn-containers-get-KILLED-automatically-MapReduce-Hive-jobs/m-p/125809#M88553 <P><A rel="user" href="https://community.cloudera.com/users/10163/clukasik.html" nodeid="10163">@clukasik</A>, <A rel="user" href="https://community.cloudera.com/users/2348/divakarreddya.html" nodeid="2348">@Divakar Annapureddy</A></P><P>This was an issue related to the JIRA - <A href="https://issues.apache.org/jira/browse/HIVE-11681">https://issues.apache.org/jira/browse/HIVE-11681</A></P><P>We have hive jobs that use same aux jars and "add jar" statements and these jobs execute concurrently. So, apparently, when one of the jobs is completed, the loader is closed while the other job is still using it and hence the KILL signal. We solved it by removing add jar statements from concurrent hive jobs and instead added the auxiliary jars in hive.aux.jars.path at the time of HS2 "start" which means that these jars would be loaded only once and will not be removed/closed/unloaded per session. Thus concurrent hive jobs will not have problem in accessing them.</P><P>To make the jars available to HS2 - they were copied on each machine that hosted HS2 and then through Ambari added the path to HIVE_AUX_JARS_PATH only for the hiveserver component in the hive-env template script.</P><P>if [ "$SERVICE" = "hiveserver2" ]; then </P><P> CUSTOM_AUX_JARS_PATH=/&lt;path_to_aux_lib_dir&gt;</P><P> if [ -d $CUSTOM_AUX_JARS_PATH ]; then </P><P> CUSTOM_AUX_JARS=`echo $CUSTOM_AUX_JARS_PATH/*.jar | sed 's/ /,/g'` </P><P> export HIVE_AUX_JARS_PATH="$HIVE_AUX_JARS_PATH,$CUSTOM_AUX_JARS" </P><P> fi </P><P>fi</P> Sun, 08 Jan 2017 19:18:19 GMT dosigary 2017-01-08T19:18:19Z