Home | About | Sematext search-lucene.com search-hadoop.com
NEW: Monitor These Apps!
elasticsearch, apache solr, apache hbase, hadoop, redis, casssandra, amazon cloudwatch, mysql, memcached, apache kafka, apache zookeeper, apache storm, ubuntu, centOS, red hat, debian, puppet labs, java, senseiDB
 Search Hadoop and all its subprojects:

Switch to Threaded View
MapReduce >> mail # user >> Why Hadoop force using DNS?


Copy link to this message
-
Why Hadoop force using DNS?
Looking at Hadoop source you can see that Hadoop relies on the fact each
node has resolvable name.

For example, Hadoop 2 namenode reverse look the up of each node that
connects to it. Also, there's no way way to tell a database to advertise an
UP as it's address. Setting datanode.network.interface to, say, eth1, would
cause Hadoop to reverse lookup UPs on eth1 and advertise the result.

Why is that? Using plain IPs is simple to set up, and I can't see a reason
not to support them?
NEW: Monitor These Apps!
elasticsearch, apache solr, apache hbase, hadoop, redis, casssandra, amazon cloudwatch, mysql, memcached, apache kafka, apache zookeeper, apache storm, ubuntu, centOS, red hat, debian, puppet labs, java, senseiDB