Hi, After I upgraded the cluster successfully to the last releases CM 5.14.0 / CDH 5.14.2, I have been faced to this problem in 6 of my nodes, suddenly in the first queries the impala deamon get stopped and the query cancelled and give the error messages below: Impala-shell: Cancelled due to unreachable impalad(s): node1.example.com:22000 ODBC: Status: RPC Error: Client for node5.example.com:22000 hit an unexpected exception: Unknown: Interrupted system call, type: N6apache6thrift9transport19TTransportExceptionE, rpc: N6impala19TTransmitDataResultE, send: done Impala Deamon log file:   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) Statestore log file: 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) When I looking for the issue source I have found this crash message in the Impala Daemon logs: # # 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. # 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: Centos 6.9 kernel: 2.6.32-696.23.1.el6.x86_64 2.6.32-696.16.1.el6.x86_64 2.6.32-696.13.2.el6.x86_64 2.6.32-642.15.1.el6.x86_64 2.6.32-642.11.1.el6.x86_64 JDK: jdk.1.8.0_144 jdk.1.8.0_121 Remark: The 6 nodes are the only nodes that does not support SSE4_2. Thanks in advance. ... View more