Mailing-List: contact user-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@hadoop.apache.org
Received-SPF: pass (nike.apache.org: domain of ed.sweeney@falkonry.com
 designates 209.85.213.181 as permitted sender)
MIME-Version: 1.0
Date: Sat, 26 Jul 2014 12:30:36 -0700
Message-ID: 
 <CAANgQeNht9-wZsVzqpUNLLsWRKesg1jHRk9HkmxDtN98ktBa9w@mail.gmail.com>
Subject: Datanode denied communication with namenode
From: Ed Sweeney <ed.sweeney@falkonry.com>
To: user@hadoop.apache.org
Content-Type: text/plain; charset=UTF-8

All,

New AWS cluster with Cloudera 4.3 RPMs.

dfs.hosts contains 3 host names, they all resolve from each of the 3 hosts.

the datanode on the same machine as the namenode starts fine (once I
added it's longname hostname to dfs.hosts file).

the 2 remote datanodes both get the error below.

org.apache.hadoop.hdfs.server.protocol.DisallowedDatanodeException:
Datanode denied communication with namenode because hostname cannot be
resolved (ip=10.0.7.61, hostname=10.0.7.61):
DatanodeRegistration(0.0.0.0,
datanodeUuid=de84029d-107b-4c80-b503-c990a3621a40,

It is AWS VPC so no reverse dns and I don't want to add anything to
the /etc/hosts files - shouldn't have to since the long and short
names all resolve properly.

Seeing hostname field in the error message has the ip field, I tried
using dfs.client.use.datanode.hostname = true but no change.

Any help appreciated!

-Ed