<?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: After upgrading to cdh 5.14.2 Impala daemon stopped suddenly! - in Archives of Support Questions (Read Only)</title>
    <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/After-upgrading-to-cdh-5-14-2-Impala-daemon-stopped-suddenly/m-p/66480#M77379</link>
    <description>Thanks for the reply Tim&lt;BR /&gt;It was CDH 5.12.0 and it was working great on the same servers..&lt;BR /&gt;I'll share the CPU info of those nodes ASAS.</description>
    <pubDate>Wed, 18 Apr 2018 01:03:20 GMT</pubDate>
    <dc:creator>AcharkiMed</dc:creator>
    <dc:date>2018-04-18T01:03:20Z</dc:date>
    <item>
      <title>After upgrading to cdh 5.14.2 Impala daemon stopped suddenly! -</title>
      <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/After-upgrading-to-cdh-5-14-2-Impala-daemon-stopped-suddenly/m-p/66472#M77377</link>
      <description>&lt;P&gt;Hi,&lt;BR /&gt;&lt;BR /&gt;After I upgraded the cluster successfully to the last releases &lt;STRONG&gt;CM 5.14.0 / CDH 5.14.2&lt;/STRONG&gt;, I have been faced to this problem in 6 of my nodes, suddenly in the first queries the &lt;STRONG&gt;impala deamon&lt;/STRONG&gt; get &lt;STRONG&gt;stopped&lt;/STRONG&gt; and the &lt;STRONG&gt;query cancelled&lt;/STRONG&gt; and give the error messages below:&lt;BR /&gt;&lt;BR /&gt;&lt;U&gt;Impala-shell:&lt;/U&gt;&lt;/P&gt;&lt;PRE&gt;Cancelled due to unreachable impalad(s): node1.example.com:22000&lt;/PRE&gt;&lt;P&gt;&lt;U&gt;ODBC:&lt;BR /&gt;&lt;/U&gt;&lt;/P&gt;&lt;PRE&gt;&lt;U&gt;Status: RPC Error: Client for node5.example.com:22000 hit an unexpected exception: Unknown: Interrupted system call, type: N6apache6thrift9transport19TTransportExceptionE, rpc: N6impala19TTransmitDataResultE, send: done&lt;/U&gt;&lt;/PRE&gt;&lt;P&gt;&lt;U&gt;Impala Deamon log file:&lt;/U&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;PRE&gt;CancelQueryFInstances query_id= 3423055f3fda78a:a2446bea00000000 failed to connect to node2.example.com:22000 :Couldn't open transport for node2.example.com:22000 (connect() failed: Connection refused)&lt;/PRE&gt;&lt;P&gt;&lt;U&gt;Statestore log file:&lt;/U&gt;&lt;/P&gt;&lt;PRE&gt;I0413 20:07:01.767758 64122 statestore.cc:729] Unable to send heartbeat message to subscriber impalad@node5.exaple.com:22000, received error: Couldn't open transport for node5.exaple.com:23000 (connect() failed: Connection refused)&lt;/PRE&gt;&lt;P&gt;&lt;BR /&gt;When I looking for the issue source I have found this &lt;U&gt;crash message&lt;/U&gt; in the &lt;U&gt;Impala Daemon logs&lt;/U&gt;:&lt;/P&gt;&lt;PRE&gt;#
# A fatal error has been detected by the Java Runtime Environment:
#
#  SIGILL (0x4) at pc=0x0000000000d863e5, pid=13065, tid=0x00007efc499cf700
#
# JRE version: Java(TM) SE Runtime Environment (8.0_144-b01) (build 1.8.0_144-b01)
# Java VM: Java HotSpot(TM) 64-Bit Server VM (25.144-b01 mixed mode linux-amd64 compressed oops)
# Problematic frame:
# C  [impalad+0x9863e5]  impala::HdfsScanNodeBase::StopAndFinalizeCounters()+0x965
#
# Failed to write core dump. Core dumps have been disabled. To enable core dumping, try "ulimit -c unlimited" before starting Java again
#
# An error report file with more information is saved as:
# /var/run/cloudera-scm-agent/process/13339-impala-IMPALAD/hs_err_pid13065.log
#
# If you would like to submit a bug report, please visit:
#   http://bugreport.java.com/bugreport/crash.jsp
# The crash happened outside the Java Virtual Machine in native code.
# See problematic frame for where to report the bug.
#&lt;/PRE&gt;&lt;P&gt;&lt;BR /&gt;We have Centos OS v6.9 in the 6 servers, I tried to upgrade/downgrade to a several centos 6.9 kernel releases and jdk versions but no result, Here is the releases used:&lt;SPAN class="short_text"&gt;&lt;SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;EM&gt;Centos 6.9 kernel:&lt;/EM&gt;&lt;BR /&gt;2.6.32-696.23.1.el6.x86_64&lt;BR /&gt;2.6.32-696.16.1.el6.x86_64&lt;BR /&gt;2.6.32-696.13.2.el6.x86_64&lt;BR /&gt;2.6.32-642.15.1.el6.x86_64&lt;BR /&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;2.6.32-642.11.1.el6.x86_64&lt;BR /&gt;&lt;BR /&gt;&lt;EM&gt;JDK:&lt;/EM&gt;&lt;BR /&gt;jdk.1.8.0_144&lt;BR /&gt;jdk.1.8.0_121&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;U&gt;Remark&lt;/U&gt;: The 6 nodes are the only nodes that does not support SSE4_2.&lt;BR /&gt;&lt;BR /&gt;Thanks in advance.&lt;/P&gt;</description>
      <pubDate>Fri, 16 Sep 2022 13:06:49 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Archives-of-Support-Questions/After-upgrading-to-cdh-5-14-2-Impala-daemon-stopped-suddenly/m-p/66472#M77377</guid>
      <dc:creator>AcharkiMed</dc:creator>
      <dc:date>2022-09-16T13:06:49Z</dc:date>
    </item>
    <item>
      <title>Re: After upgrading to cdh 5.14.2 Impala daemon stopped suddenly! -</title>
      <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/After-upgrading-to-cdh-5-14-2-Impala-daemon-stopped-suddenly/m-p/66478#M77378</link>
      <description>&lt;P&gt;What version of CDH were you running before the upgrade? Were you running on the same hardware?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Can you include the CPU info from your impalad.INFO log. It looks something like this:&lt;/P&gt;&lt;PRE&gt;I0417 17:05:31.064653  8873 init.cc:237] Cpu Info:
  Model: Intel(R) Core(TM) i7-4790 CPU @ 3.60GHz
  Cores: 8
  Max Possible Cores: 8
  L1 Cache: 32.00 KB (Line: 64.00 B)
  L2 Cache: 256.00 KB (Line: 64.00 B)
  L3 Cache: 8.00 MB (Line: 64.00 B)
  Hardware Supports:
    ssse3
    sse4_1
    sse4_2
    popcnt
    avx
    avx2
    pclmulqdq
  Numa Nodes: 1
  Numa Nodes of Cores: 0-&amp;gt;0 | 1-&amp;gt;0 | 2-&amp;gt;0 | 3-&amp;gt;0 | 4-&amp;gt;0 | 5-&amp;gt;0 | 6-&amp;gt;0 | 7-&amp;gt;0 |&lt;/PRE&gt;</description>
      <pubDate>Wed, 18 Apr 2018 00:09:28 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Archives-of-Support-Questions/After-upgrading-to-cdh-5-14-2-Impala-daemon-stopped-suddenly/m-p/66478#M77378</guid>
      <dc:creator>Tim Armstrong</dc:creator>
      <dc:date>2018-04-18T00:09:28Z</dc:date>
    </item>
    <item>
      <title>Re: After upgrading to cdh 5.14.2 Impala daemon stopped suddenly! -</title>
      <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/After-upgrading-to-cdh-5-14-2-Impala-daemon-stopped-suddenly/m-p/66480#M77379</link>
      <description>Thanks for the reply Tim&lt;BR /&gt;It was CDH 5.12.0 and it was working great on the same servers..&lt;BR /&gt;I'll share the CPU info of those nodes ASAS.</description>
      <pubDate>Wed, 18 Apr 2018 01:03:20 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Archives-of-Support-Questions/After-upgrading-to-cdh-5-14-2-Impala-daemon-stopped-suddenly/m-p/66480#M77379</guid>
      <dc:creator>AcharkiMed</dc:creator>
      <dc:date>2018-04-18T01:03:20Z</dc:date>
    </item>
    <item>
      <title>Re: After upgrading to cdh 5.14.2 Impala daemon stopped suddenly! -</title>
      <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/After-upgrading-to-cdh-5-14-2-Impala-daemon-stopped-suddenly/m-p/66501#M77380</link>
      <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://community.cloudera.com/t5/user/viewprofilepage/user-id/11593"&gt;@Tim Armstrong&lt;/a&gt;&lt;BR /&gt;&lt;BR /&gt;Here is the CPU info&amp;nbsp;from impalad.INFO :&lt;/P&gt;&lt;PRE&gt;I0417 20:54:12.845438 13375 init.cc:230] Cpu Info:
  Model: Intel(R) Xeon(R) CPU           E5405  @ 2.00GHz
  Cores: 8
  Max Possible Cores: 8
  L1 Cache: 32.00 KB (Line: 64.00 B)
  L2 Cache: 6.00 MB (Line: 64.00 B)
  L3 Cache: 0 (Line: 0)
  Hardware Supports:
    ssse3
    sse4_1
  Numa Nodes: 1
  Numa Nodes of Cores: 0-&amp;gt;0 | 1-&amp;gt;0 | 2-&amp;gt;0 | 3-&amp;gt;0 | 4-&amp;gt;0 | 5-&amp;gt;0 | 6-&amp;gt;0 | 7-&amp;gt;0 |&lt;/PRE&gt;&lt;P&gt;&lt;SPAN&gt;&lt;BR /&gt;&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;/P&gt;</description>
      <pubDate>Wed, 18 Apr 2018 08:46:20 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Archives-of-Support-Questions/After-upgrading-to-cdh-5-14-2-Impala-daemon-stopped-suddenly/m-p/66501#M77380</guid>
      <dc:creator>AcharkiMed</dc:creator>
      <dc:date>2018-04-18T08:46:20Z</dc:date>
    </item>
    <item>
      <title>Re: After upgrading to cdh 5.14.2 Impala daemon stopped suddenly! -</title>
      <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/After-upgrading-to-cdh-5-14-2-Impala-daemon-stopped-suddenly/m-p/66537#M77381</link>
      <description>&lt;P&gt;Do you have the JVM error dump file?&lt;/P&gt;&lt;PRE&gt;/var/run/cloudera-scm-agent/process/13339-impala-IMPALAD/hs_err_pid13065.log&lt;/PRE&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I filed &lt;A href="https://issues.apache.org/jira/browse/IMPALA-6882" target="_blank"&gt;https://issues.apache.org/jira/browse/IMPALA-6882&lt;/A&gt; to investigate the issue. I took a look at the code and it doesn't look like anything has changed, so probabyl requires deeper investigation.&lt;/P&gt;</description>
      <pubDate>Wed, 18 Apr 2018 21:41:40 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Archives-of-Support-Questions/After-upgrading-to-cdh-5-14-2-Impala-daemon-stopped-suddenly/m-p/66537#M77381</guid>
      <dc:creator>Tim Armstrong</dc:creator>
      <dc:date>2018-04-18T21:41:40Z</dc:date>
    </item>
    <item>
      <title>Re: After upgrading to cdh 5.14.2 Impala daemon stopped suddenly! -</title>
      <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/After-upgrading-to-cdh-5-14-2-Impala-daemon-stopped-suddenly/m-p/66550#M77382</link>
      <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://community.cloudera.com/t5/user/viewprofilepage/user-id/11593"&gt;@Tim Armstrong&lt;/a&gt;&lt;BR /&gt;&lt;BR /&gt;Thank you for you interaction.&lt;BR /&gt;&lt;BR /&gt;Here is the&amp;nbsp;&lt;SPAN&gt;JVM error dump file&lt;/SPAN&gt;: &lt;A href="https://ufile.io/j0zat" target="_self"&gt;https://ufile.io/j0zat&lt;BR /&gt;&lt;/A&gt;I have formatted 2 servers and resit them to the centos 6.9 (kernel 2.6.32-696.23.1.el6.x86_64) but always the same problem!&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;I hope we can resolve this bug asap, good luck.&lt;/P&gt;</description>
      <pubDate>Thu, 19 Apr 2018 09:07:25 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Archives-of-Support-Questions/After-upgrading-to-cdh-5-14-2-Impala-daemon-stopped-suddenly/m-p/66550#M77382</guid>
      <dc:creator>AcharkiMed</dc:creator>
      <dc:date>2018-04-19T09:07:25Z</dc:date>
    </item>
    <item>
      <title>Re: After upgrading to cdh 5.14.2 Impala daemon stopped suddenly! -</title>
      <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/After-upgrading-to-cdh-5-14-2-Impala-daemon-stopped-suddenly/m-p/69068#M77383</link>
      <description>&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I am running into the same problem on a fresh install of CDH 5.14.3.&amp;nbsp; According to the ticket that Tim pasted above, the issue is fixed.&amp;nbsp; Is there a timeline for when this fix will be available for general release?&amp;nbsp; Is there a workaround for this that one can utilize now?&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 13 Jun 2018 23:47:23 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Archives-of-Support-Questions/After-upgrading-to-cdh-5-14-2-Impala-daemon-stopped-suddenly/m-p/69068#M77383</guid>
      <dc:creator>AntonyN</dc:creator>
      <dc:date>2018-06-13T23:47:23Z</dc:date>
    </item>
    <item>
      <title>Re: After upgrading to cdh 5.14.2 Impala daemon stopped suddenly! -</title>
      <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/After-upgrading-to-cdh-5-14-2-Impala-daemon-stopped-suddenly/m-p/69074#M77384</link>
      <description>&lt;P&gt;I expect it will be included in the 5.14.4 maintenance release. I'm not aware of a workaround aside from avoiding running on affected hardware without popcnt support.&lt;/P&gt;</description>
      <pubDate>Thu, 14 Jun 2018 02:03:12 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Archives-of-Support-Questions/After-upgrading-to-cdh-5-14-2-Impala-daemon-stopped-suddenly/m-p/69074#M77384</guid>
      <dc:creator>Tim Armstrong</dc:creator>
      <dc:date>2018-06-14T02:03:12Z</dc:date>
    </item>
    <item>
      <title>Re: After upgrading to cdh 5.14.2 Impala daemon stopped suddenly! -</title>
      <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/After-upgrading-to-cdh-5-14-2-Impala-daemon-stopped-suddenly/m-p/77006#M77385</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I am happy to state that after updating to CDH 5.14.4, that this crash bug seems to be fixed.&amp;nbsp; We can run Impala queries now!&amp;nbsp; This is the first we've used Impala and it looks amazingly fast - glad we can use it now &lt;span class="lia-unicode-emoji" title=":slightly_smiling_face:"&gt;🙂&lt;/span&gt;&amp;nbsp; Thank you for fixing!&lt;/P&gt;</description>
      <pubDate>Mon, 16 Jul 2018 20:12:49 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Archives-of-Support-Questions/After-upgrading-to-cdh-5-14-2-Impala-daemon-stopped-suddenly/m-p/77006#M77385</guid>
      <dc:creator>AntonyN</dc:creator>
      <dc:date>2018-07-16T20:12:49Z</dc:date>
    </item>
    <item>
      <title>Re: After upgrading to cdh 5.14.2 Impala daemon stopped suddenly! -</title>
      <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/After-upgrading-to-cdh-5-14-2-Impala-daemon-stopped-suddenly/m-p/77007#M77386</link>
      <description>&lt;P&gt;&lt;a href="https://community.cloudera.com/t5/user/viewprofilepage/user-id/27581"&gt;@AntonyN&lt;/a&gt;thanks for following up - glad to hear it!&lt;/P&gt;</description>
      <pubDate>Mon, 16 Jul 2018 20:37:35 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Archives-of-Support-Questions/After-upgrading-to-cdh-5-14-2-Impala-daemon-stopped-suddenly/m-p/77007#M77386</guid>
      <dc:creator>Tim Armstrong</dc:creator>
      <dc:date>2018-07-16T20:37:35Z</dc:date>
    </item>
  </channel>
</rss>

