On BDA the Impala Daemon on One Node Can Not Start Due to Problem Binding to Port 22000-Fails with "backend (on port: 22000) did not start correctly" (Doc ID 2120473.1)

Last updated on MARCH 25, 2016

Applies to:

Big Data Appliance Integrated Software - Version 4.2.0 and later
Linux x86-64

Symptoms

On BDA V4.2/CDH 5.4.0 the impala daemon on one node can not start due to a problem
binding to port 22000 (The port used by impala daemons to communicate with each other.)

Symptoms show:

1. The impala daemon tries to start but ends up giving the following error as seen in /var/log/impalad on the node.  From /var/log/impalad ERROR file:

Log file created at: 2016/03/02 15:14:06
Running on machine: <host>.example.com
Log line format: [IWEF]mmdd hh:mm:ss.uuuuuu threadid file:line] msg
E0302 15:14:06.033330 13908 logging.cc:119] stderr will be logged to this file.
E0302 15:14:08.167940 14031 thrift-server.cc:157] ThriftServer 'backend' (on port: 22000) exited due to TException: Could not bind: Transport endpoint is not connected
E0302 15:14:08.168010 13908 thrift-server.cc:146] ThriftServer 'backend' (on port: 22000) did not start correctly
E0302 15:14:08.168669 13908 impalad-main.cc:75] ThriftServer 'backend' (on port: 22000) did not start correctly

2. It is observed that the impala daemon itself is using the port on this host, not another process.  If the daemon is killed another one starts and uses the port.

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms