Hostnames in impala

On Thu, Jan 16, 2014 at 5:11 PM, Sammy Yu wrote:

Hi,
I'm running impala 1.2.3 with CDH4 on Amazon Web Services. I
noticed that every once in a while the number of backends will drop.
I took a closer look at it and it seems to be DNS related
(/var/log/impala/impala-server.log):
E0116 16:27:11.169425 1255 data-stream-sender.cc:281] channel send
status: Couldn't open transport for ip-10-91-37-128:22000(Could not
resolve host for client socket.)

AWS instances launched can have either the ec2.internal or
compute-1.internal subdomain. It seems like impala is just using the
leaf domain so
ip-10-88-13-94.ec2.internal becomes ip-10-88-13-94
and
domU-12-31-38-04-7C-AB.compute-1.internal becomes domU-12-31-38-04-7C-AB

This causes problem when the impalad tries to communicate with one
another and state server with the shorten hostname. Is there an easy
solution such as using IP address or fully qualified hostname instead?

Thanks,
Sammy

To unsubscribe from this group and stop receiving emails from it, send an
email to impala-user+unsubscribe@cloudera.org.