Raj's almost right. In times of high load or space fillup on a local
DN, the NameNode may decide to instead pick a non-local DN for
replica-writing. In this way, the Node A may get a "copy 0" of a
replica from a task. This is per the default block placement policy.
P.s. Note that HDFS hardly makes
Thanks, Raj you got exactly my point. I wanted to confirm this assumption as
I was guessing if a shared HDFS cluster with MR and Hbase like this would
make sense:
http://old.nabble.com/HBase-User-f34655.html
--
View this message in context:
http://lucene.472066.n3.nabble.com/doubt-about-reduce-