Created on 05-07-2014 03:02 PM - edited 09-16-2022 01:58 AM
I get the below error on impala 1.2.3 version. I did the recycle of all the impalad on cluster but still I get the below error when use “select * tablename” but same select statement works from hive.
ERROR: ExecPlanRequest rpc query_id=8641141086f3ab8e:8ff3926e0f221e91 instance_id=8641141086f3ab8e:8ff3926e0f221e95 failed: ECONNRESET
I have not seen this error before but I ran out of disk space on couple of nodes and I think it caused this issue.
Thanks,
Ram
Created 05-08-2014 03:30 PM
Hello All,
It was because of port conflict with other services running the server (impala daemon backend port be_port) 22000 has conflict on new services installed on linux server.
The strange think is CM shows all "GREEN" and all the process has been started but when you look at the log file it will show the following error -
+ exec /usr/lib/impala/../../bin/impalad --flagfile=/var/run/cloudera-scm-agent/process/2050-impala-IMPALAD/impala-conf/impalad_flags
E0508 18:20:58.253557 16729 thrift-server.cc:157] ThriftServer 'backend' (on port: 22000) exited due to TException: Could not bind: Transport endpoint is not connected
E0508 18:20:58.254359 16152 thrift-server.cc:146] ThriftServer 'backend' (on port: 22000) did not start correctly
please make life easier 🙂
Thanksm
Ram
Created 05-08-2014 10:01 AM
Created 05-08-2014 11:56 AM
Created 05-08-2014 12:08 PM
Created 05-08-2014 12:15 PM
Created 05-08-2014 03:30 PM
Hello All,
It was because of port conflict with other services running the server (impala daemon backend port be_port) 22000 has conflict on new services installed on linux server.
The strange think is CM shows all "GREEN" and all the process has been started but when you look at the log file it will show the following error -
+ exec /usr/lib/impala/../../bin/impalad --flagfile=/var/run/cloudera-scm-agent/process/2050-impala-IMPALAD/impala-conf/impalad_flags
E0508 18:20:58.253557 16729 thrift-server.cc:157] ThriftServer 'backend' (on port: 22000) exited due to TException: Could not bind: Transport endpoint is not connected
E0508 18:20:58.254359 16152 thrift-server.cc:146] ThriftServer 'backend' (on port: 22000) did not start correctly
please make life easier 🙂
Thanksm
Ram
Created 05-09-2014 09:13 AM
Created 06-03-2016 01:29 AM
Hi,
We are facing the same exception on a running , on one of the nodes. We are running on Impala version 2.3. As per above update this issue should have resolved in Impala 1.4. Please help as it is impacting stability of cluster. All nodes stops responding even though problem is only with one node.
Exception:
E0602 09:30:30.544390 18138 logging.cc:120] stderr will be logged to this file.
E0602 09:30:39.605379 18220 thrift-server.cc:160] ThriftServer 'backend' (on port: 22000) exited duelp e to TException: Could not $
E0602 09:30:39.605533 18138 thrift-server.cc:149] ThriftServer 'backend' (on port: 22000) did not start correctly
E0602 09:30:39.605597 18138 impalad-main.cc:76] ThriftServer 'backend' (on port: 22000)
Created 06-03-2016 03:30 AM
Created 06-03-2016 03:56 AM
1- When we started impala service it started fine. Please see statestored.info file. I have removed my actual server name. And it was working fine. Suddenly on 02-Jun 07:53:09 it was unable to send heartbeat. And at 9:30 we see error I posted earlier about ThriftServer.
2- so nothing was running on port 22000.
namenode->statestored.info
I0506 14:46:35.929142 4306 statestore.cc:370] Registering: impalad@<node name which got impacted>:22000
I0506 14:46:35.929231 4306 statestore.cc:393] Subscriber 'impalad@<node name which got impacted>:22000' registered (registration id: fc490552ddd59468:113b9a75e4b55787)
I0602 07:53:09.326907 4153 statestore.cc:690] Unable to send heartbeat message to subscriber impalad@<node name which got impacted>:22000, received error: RPC timed out
I0602 07:53:13.325565 4153 statestore.cc:690] Unable to send heartbeat message to subscriber impalad@<node name which got impacted>:22000, received error: RPC timed out
I0602 07:53:17.321043 4153 statestore.cc:690] Unable to send heartbeat message to subscriber impalad@<node name which got impacted>:22000, received error: RPC timed out
I0602 07:53:21.320971 4153 statestore.cc:690] Unable to send heartbeat message to subscriber impalad@<node name which got impacted>:22000, received error: RPC timed out
I0602 07:53:25.320952 4153 statestore.cc:690] Unable to send heartbeat message to subscriber impalad@<node name which got impacted>:22000, received error: RPC timed out
I0602 07:53:29.320972 4153 statestore.cc:690] Unable to send heartbeat message to subscriber impalad@<node name which got impacted>:22000, received error: RPC timed out
I0602 07:53:33.320968 4153 statestore.cc:690] Unable to send heartbeat message to subscriber impalad@<node name which got impacted>:22000, received error: RPC timed out
I0602 07:53:37.320973 4153 statestore.cc:690] Unable to send heartbeat message to subscriber impalad@<node name which got impacted>:22000, received error: RPC timed out
I0602 07:53:41.316970 4153 statestore.cc:690] Unable to send heartbeat message to subscriber impalad@<node name which got impacted>:22000, received error: RPC timed out
I0602 07:53:45.316970 4153 statestore.cc:690] Unable to send heartbeat message to subscriber impalad@<node name which got impacted>:22000, received error: RPC timed out
I0602 07:53:49.316972 4153 statestore.cc:690] Unable to send heartbeat message to subscriber impalad@<node name which got impacted>:22000, received error: RPC timed out
I0602 07:53:49.316988 4153 statestore.cc:702] Subscriber 'impalad@<node name which got impacted>:22000' has failed, disconnected or re-registered (last known registration ID: impal$
I0602 10:09:16.522661 17361 statestore.cc:370] Registering: impalad@<node name which got impacted>:22000
I0602 10:09:16.522711 17361 statestore.cc:393] Subscriber 'impalad@<node name which got impacted>:22000' registered (registration id: f45a9be0d38a32c:63a32de772688380)
Created 06-03-2016 04:38 AM
Created on 06-03-2016 05:14 AM - edited 06-03-2016 05:16 AM
We already shared exception from Impala logs of affected node. But "ThriftServer" log came about 90 minutes later when node connection was lost. There is no other error/exception in impala log.
Please let me know if there is some other log we can check into. This event happened multiple times. In one node the service is down but we still see process running. See attachment.
Even kill -9 pid is not honoring.
Also when one node is impacted my application running on Weblogic 11g looses all connection and we had to restart application servers for getting connection back. This is becoming annoying.
Please let me know what we can do to get to root cause of problem.
Created 06-03-2016 05:52 AM
Created 09-14-2017 05:29 AM
/var/log/impalad/impalad.WARNING
E0914 10:58:10.457620 94112 logging.cc:121] stderr will be logged to this file.
W0914 10:58:10.467237 94112 authentication.cc:1003] LDAP authentication is being used with TLS, but without an --ldap_ca_certificate file, the identity of the LDAP server cannot be verified. Network communication (and hence passwords) could be intercepted by a man-in-the-middle attack
E0914 10:58:13.220167 94268 thrift-server.cc:182] ThriftServer 'backend' (on port: 22000) exited due to TException: Could not bind: Transport endpoint is not connected
E0914 10:58:13.220221 94112 thrift-server.cc:171] ThriftServer 'backend' (on port: 22000) did not start correctly
F0914 10:58:13.221709 94112 impalad-main.cc:89] ThriftServer 'backend' (on port: 22000) did not start correctly
. Impalad exiting.
Can you help me?
Created on 08-28-2018 01:47 PM - edited 08-28-2018 01:50 PM
there is a possibility that your daemon process is hung
find it and kill it
$> ps -eaf|grep impala
impala 4399 1 0 Aug17 ? 00:00:00 python2.7 /usr/lib64/cmf/agent/build/env/bin/cmf-redactor /usr/lib64/cmf/service/impala/impala.sh impalad impalad_flags false
clouder+ 8426 5709 0 16:34 pts/0 00:00:00 grep --color=auto impala
impala 12322 1 0 Aug17 ? 00:00:00 /opt/cloudera/parcels/CDH-5.10.1-1.cdh5.10.1.p0.10/lib/impala/sbin-retail/impalad --flagfile=/run/cloudera-scm-agent/process/3639-impala-IMPALAD/impala-conf/impalad_flags
$>sudo kill -9 12322
$>sudo kill -9 4399
try to restart your daemon
and check the port
$> sudo netstat -lntp|grep 22000