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
HDFS >> mail # user >> Intelligence of decommission


Copy link to this message
-
Intelligence of decommission
Hi.

As I sit here and wait for node decommission to finish, I was wondering
about the intelligence of the decision making.  [The name nodes, not mine.
:) ]

Let's say I have the following scenario:

I have two files.  Both files consist of one block with a replication factor
of three.  I decommission two nodes.  File #1 has two of its replicas on the
two nodes I am decommissioning.  File #2 has only one of its replicas on one
of the two nodes I am decommissioning.

Is the block with two replicas on the two nodes I am decommissioning given
priority?  How does the name node decide which blocks to re-replicate first?

Thanks.
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