<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>question Re: Yarn containers get KILLED automatically. MapReduce/Hive jobs fail in Support Questions</title>
    <link>https://community.cloudera.com/t5/Support-Questions/Yarn-containers-get-KILLED-automatically-MapReduce-Hive-jobs/m-p/125805#M88549</link>
    <description>&lt;P&gt;&lt;A rel="user" href="https://community.cloudera.com/users/10163/clukasik.html" nodeid="10163"&gt;@clukasik&lt;/A&gt; This is for sure that no one has issued the yarn kill command. Moreover, the machine 172.23.35.6 is a machine where only master services are running. And access is restricted to this machine. The services on this machine are -&lt;/P&gt;&lt;P&gt;namenode, hive_server, hive_metastore, journalnode, kerberos_client,mapreduce2_client,&lt;/P&gt;&lt;P&gt;falcon_client, hbase_client, hbase_master, hcat, hdfs_client, hive_client, mahout, metrics_monitor, oozie_client, phoenix_query_server, pig, ranger_admin, ranger_usersync, resourcemanager, spark_client, spark_thriftserver, sqoop, tez_client, webhcat_server, yarn_client, zkfc, zookeeper_client, zookeeper_server&lt;/P&gt;&lt;P&gt;Since these are hive jobs, there could be a possibility that hive_server itself is issuing sort of a kill command. Not sure though - will check hive logs as well.&lt;/P&gt;</description>
    <pubDate>Wed, 30 Nov 2016 14:50:01 GMT</pubDate>
    <dc:creator>dosigary</dc:creator>
    <dc:date>2016-11-30T14:50:01Z</dc:date>
  </channel>
</rss>

