@hadoop.apache.org
Subject: Re: Namenode fails to replicate file
Doesn't the -setrep command force the replication to be increased
immediately?
./hadoop dfs -setrep [replication] path
(I may have misunderstood)
On Thu, 2008-02-07 at 17:05 -0800, Ted Dunning wrote:
Chris Kline reported
It doesn't happen immediately. It happens SLOWLY.
On 2/7/08 11:05 PM, Tim Wintle [EMAIL PROTECTED] wrote:
Doesn't the -setrep command force the replication to be increased
immediately?
./hadoop dfs -setrep [replication] path
(I may have misunderstood)
On Thu, 2008-02-07 at 17:05
Ted Dunning wrote:
That makes it wait, but I don't think it increases the urgency on the part
of the namenode.
As an interesting experiment, I had a cluster with lots of pending
replication to do that was happening slowly. Restarting the name node
caused the rate of replication to increase
I will see if I can replicate the problem and do as you suggest.
On 2/8/08 4:29 PM, Raghu Angadi [EMAIL PROTECTED] wrote:
Ted Dunning wrote:
That makes it wait, but I don't think it increases the urgency on the part
of the namenode.
As an interesting experiment, I had a cluster with
Chris Kline reported a problem in early January where a file which had too
few replicated blocks did not get replicated until a DFS restart.
I just saw a similar issue. I had a file that had a block with 1 replica (2
required) that did not get replicated. I changed the number of required
Doesn't the -setrep command force the replication to be increased
immediately?
./hadoop dfs -setrep [replication] path
(I may have misunderstood)
On Thu, 2008-02-07 at 17:05 -0800, Ted Dunning wrote:
Chris Kline reported a problem in early January where a file which had too
few replicated
