<?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/125806#M88550</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; &lt;/P&gt;&lt;P&gt;I checked the hiveserver logs. Found that corresponding to all these MapReduce failures for Hive jobs, there was always a FATAL error that occured in hive before the kill signal was seen in MapReduce logs. The stack trace for this particular error is attached in the "hiveserver2-logs-error.txt" and the activities of the thread is where it happened is available in "thread-logs.txt". &lt;/P&gt;&lt;P&gt;On further investigation, it was also found that the attached error can be related(traced back) to an unresolved JIRA -&lt;/P&gt;&lt;UL&gt;
&lt;LI&gt;&lt;A href="http://osdir.com/ml/general/2015-08/msg39276.html"&gt;http://osdir.com/ml/general/2015-08/msg39276.html&lt;/A&gt;&lt;/LI&gt;&lt;LI&gt;&lt;A href="https://issues.apache.org/jira/browse/HIVE-11681"&gt;https://issues.apache.org/jira/browse/HIVE-11681&lt;/A&gt;&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;Please let me know your thoughts on this.&lt;/P&gt;</description>
    <pubDate>Wed, 30 Nov 2016 17:17:13 GMT</pubDate>
    <dc:creator>dosigary</dc:creator>
    <dc:date>2016-11-30T17:17:13Z</dc:date>
  </channel>
</rss>

