<?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: Diagnostics: Container killed on request. Exit code is 143 Container exited with a non-zero exit code 143. in Support Questions</title>
    <link>https://community.cloudera.com/t5/Support-Questions/Diagnostics-Container-killed-on-request-Exit-code-is-143/m-p/240930#M202734</link>
    <description>&lt;P&gt;&lt;A rel="user" href="https://community.cloudera.com/users/114192/shindoyasuhiro.html" nodeid="114192"&gt;@Yasuhiro Shindo&lt;/A&gt;&lt;/P&gt;&lt;P&gt;Container killed exit code most of the time is due to memory overhead&lt;/P&gt;&lt;P&gt;If you haven't specified &lt;STRONG&gt;spark.yarn.driver.memoryOverhead or spark.yarn.executor.memoryOverhead&lt;/STRONG&gt; these params in your spark submit then add these params (or) if you have specified then increase the already configured value.&lt;/P&gt;&lt;P&gt;Please refer to &lt;A rel="noopener noreferrer noopener noreferrer" href="https://stackoverflow.com/questions/41057311/the-value-of-spark-yarn-executor-memoryoverhead-setting" target="_blank"&gt;this&lt;/A&gt; link to decide overhead value.&lt;/P&gt;</description>
    <pubDate>Fri, 24 May 2019 11:36:24 GMT</pubDate>
    <dc:creator>Shu_ashu</dc:creator>
    <dc:date>2019-05-24T11:36:24Z</dc:date>
    <item>
      <title>Diagnostics: Container killed on request. Exit code is 143 Container exited with a non-zero exit code 143.</title>
      <link>https://community.cloudera.com/t5/Support-Questions/Diagnostics-Container-killed-on-request-Exit-code-is-143/m-p/240929#M202733</link>
      <description>&lt;P&gt;Yarn Application status was failed, and displayed follows.&lt;/P&gt;&lt;PRE&gt;Diagnostics: Container killed on request. Exit code is 143 Container exited with a non-zero exit code 143.&lt;/PRE&gt;&lt;P&gt;And Yarn Log Entries includes following message.&lt;/P&gt;&lt;PRE&gt;ERROR CoarseGrainedExecutorBackend: Executor self-exiting due to : Driver XX.XX.XX.XX:46869 disassociated! Shutting down.
INFO DiskBlockManager: Shutdown hook called&lt;/PRE&gt;&lt;P&gt;Could you tell me the checkpoint to solve this problem?&lt;/P&gt;&lt;P&gt;Best Regards.&lt;/P&gt;</description>
      <pubDate>Thu, 23 May 2019 17:00:55 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Support-Questions/Diagnostics-Container-killed-on-request-Exit-code-is-143/m-p/240929#M202733</guid>
      <dc:creator>shindo_yasuhiro</dc:creator>
      <dc:date>2019-05-23T17:00:55Z</dc:date>
    </item>
    <item>
      <title>Re: Diagnostics: Container killed on request. Exit code is 143 Container exited with a non-zero exit code 143.</title>
      <link>https://community.cloudera.com/t5/Support-Questions/Diagnostics-Container-killed-on-request-Exit-code-is-143/m-p/240930#M202734</link>
      <description>&lt;P&gt;&lt;A rel="user" href="https://community.cloudera.com/users/114192/shindoyasuhiro.html" nodeid="114192"&gt;@Yasuhiro Shindo&lt;/A&gt;&lt;/P&gt;&lt;P&gt;Container killed exit code most of the time is due to memory overhead&lt;/P&gt;&lt;P&gt;If you haven't specified &lt;STRONG&gt;spark.yarn.driver.memoryOverhead or spark.yarn.executor.memoryOverhead&lt;/STRONG&gt; these params in your spark submit then add these params (or) if you have specified then increase the already configured value.&lt;/P&gt;&lt;P&gt;Please refer to &lt;A rel="noopener noreferrer noopener noreferrer" href="https://stackoverflow.com/questions/41057311/the-value-of-spark-yarn-executor-memoryoverhead-setting" target="_blank"&gt;this&lt;/A&gt; link to decide overhead value.&lt;/P&gt;</description>
      <pubDate>Fri, 24 May 2019 11:36:24 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Support-Questions/Diagnostics-Container-killed-on-request-Exit-code-is-143/m-p/240930#M202734</guid>
      <dc:creator>Shu_ashu</dc:creator>
      <dc:date>2019-05-24T11:36:24Z</dc:date>
    </item>
    <item>
      <title>Re: Diagnostics: Container killed on request. Exit code is 143 Container exited with a non-zero exit code 143.</title>
      <link>https://community.cloudera.com/t5/Support-Questions/Diagnostics-Container-killed-on-request-Exit-code-is-143/m-p/240931#M202735</link>
      <description>&lt;P&gt;Shu-san&lt;/P&gt;&lt;P&gt;Thank you for your early response.&lt;BR /&gt;I will feedback to my team members about this matter.&lt;/P&gt;&lt;P&gt;I'll let you know if I have any questions.&lt;/P&gt;&lt;P&gt;Best Regards.&lt;/P&gt;</description>
      <pubDate>Fri, 24 May 2019 15:11:56 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Support-Questions/Diagnostics-Container-killed-on-request-Exit-code-is-143/m-p/240931#M202735</guid>
      <dc:creator>shindo_yasuhiro</dc:creator>
      <dc:date>2019-05-24T15:11:56Z</dc:date>
    </item>
    <item>
      <title>Re: Diagnostics: Container killed on request. Exit code is 143 Container exited with a non-zero exit code 143.</title>
      <link>https://community.cloudera.com/t5/Support-Questions/Diagnostics-Container-killed-on-request-Exit-code-is-143/m-p/269842#M207129</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;Exit code 143 is related to Memory/GC issues.&amp;nbsp;Your default Mapper/reducer memory setting may not be sufficient to run the large data set. Thus, try setting up higher AM, MAP and REDUCER memory when a large yarn job is invoked.&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;For more please refer to this link.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;&lt;A href="https://stackoverflow.com/questions/42972908/container-killed-by-the-applicationmaster-exit-code-is-143" target="_blank"&gt;https://stackoverflow.com/questions/42972908/container-killed-by-the-applicationmaster-exit-code-is-143&lt;/A&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;Thanks&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;AKR&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Thu, 05 Sep 2019 15:34:04 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Support-Questions/Diagnostics-Container-killed-on-request-Exit-code-is-143/m-p/269842#M207129</guid>
      <dc:creator>AKR</dc:creator>
      <dc:date>2019-09-05T15:34:04Z</dc:date>
    </item>
  </channel>
</rss>

