Created on 09-14-2017 05:36 AM - edited 09-16-2022 05:14 AM
Impala Shell v2.7.0-cdh5.10.1
/var/log/impalad/impalad.WARNING
Log line format: [IWEF]mmdd hh:mm:ss.uuuuuu threadid file:line] msg
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.
/var/log/impalad/impalad.ERROR
E0914 10:58:10.457620 94112 logging.cc:121] stderr will be logged to this file.
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.
*** Check failure stack trace: ***
@ 0x1b566ad (unknown)
@ 0x1b58fd6 (unknown)
@ 0x1b561cd (unknown)
@ 0x1b59a7e (unknown)
@ 0xb246ec (unknown)
@ 0x7d12f3 (unknown)
@ 0x7fb5ed93ab15 __libc_start_main
@ 0x80225d (unknown)
Picked up JAVA_TOOL_OPTIONS:
Wrote minidump to /var/log/impala-minidumps/impalad/1d64946f-d7e0-cedf-19531ffd-1349463b.dmp
Created 09-18-2017 06:00 PM
We've seen this before when a bug caused a zombie impalad process to get stuck listening on port 22000. It's worth seeing if one is stilll hanging around and if so, running kill -9 on it.
Created 09-18-2017 06:00 PM
We've seen this before when a bug caused a zombie impalad process to get stuck listening on port 22000. It's worth seeing if one is stilll hanging around and if so, running kill -9 on it.
Created 09-21-2017 04:56 AM
Before your reply I've rebooted the node after that it's run well.
Now I can see some issue(Port running on other Node) again when I'm running the COMPUTE STATS command on Impala.
COMPUTE STATS:
1.I have a table with old Parquet data.
2.Now I have added parquet data with New data types(INT TO STRING) for the same columns.
3.I have created new table in the same location with new schema
(Impala > CREATE EXTERNAL TABLE database.table2 like parquet '/home/output/university/client=england/campaign=second/details=students/part-r-00111-5fce6c4d-784e-457f-9a01-aa6d6ec1187c.snappy.parquet';
Impala > SHOW CREATE TABLE table2;
Then Ive created tablw with table2 schema)
4. /home/output/university/client=england/campaign=second/details=students/part-r-00111-5fce6c4d-784e-457f-9a01-aa6d6ec1187c.snappy.parquet' has an incompatible Parquet schema for column 'mobistat.psrvoicecdma.systemid'. Column type: STRING, Parquet schema:
optional int32 systemid [i:22 d:1 r:0]
please help me out in this.