Support Questions
Find answers, ask questions, and share your expertise
Announcements
Alert: Welcome to the Unified Cloudera Community. Former HCC members be sure to read and learn how to activate your account here.

Impala: Frequent "Error communicating with impalad: TSocket read 0 bytes" errors

Impala: Frequent "Error communicating with impalad: TSocket read 0 bytes" errors

New Contributor

Experiencing frequent errors during table inserts using Impala shell via Oozie.

 

We are on CDH 5.3.1 and running Impala behind a load balancer.

 

Starting Impala Shell without Kerberos authentication
Connected to <removed>
Server version: impalad version 2.1.1-cdh5 RELEASE (build 7901877736e29716147c4804b0841afc4ebc9037)

 

Error communicating with impalad: TSocket read 0 bytes
Could not execute command: insert into table

 

Originally I thought this might be memory related, but even smaller queries that run fine via Hue interface are generating this error. It is very intermittent. Any help leading me in the right direction to troubleshoot would be very helpful.

2 REPLIES 2

Re: Impala: Frequent "Error communicating with impalad: TSocket read 0 bytes" errors

New Contributor

We are seeing this error on CDH 5.4.3


@swallace wrote:

Experiencing frequent errors during table inserts using Impala shell via Oozie.

 

We are on CDH 5.3.1 and running Impala behind a load balancer.

 

Starting Impala Shell without Kerberos authentication
Connected to <removed>
Server version: impalad version 2.1.1-cdh5 RELEASE (build 7901877736e29716147c4804b0841afc4ebc9037)

 

Error communicating with impalad: TSocket read 0 bytes
Could not execute command: insert into table

 

Originally I thought this might be memory related, but even smaller queries that run fine via Hue interface are generating this error. It is very intermittent. Any help leading me in the right direction to troubleshoot would be very helpful.


 

Re: Impala: Frequent "Error communicating with impalad: TSocket read 0 bytes" errors

Master Collaborator
This error can have multiple causes - in general it happens when there is
some problem with connection between your shell and Impala. It could be a
network interruption, some kind of misconfiguration if you're running with
Kerberos enabled on your cluster, or it could be some kind of error on
Impala's side. Typically you would diagnose by looking at the Impala logs,
the Impala debug webpage or Cloudera manager to see what caused the
interrupted connection.

- Tim