Hi, I changed replication for the entire hdfs to 2, and then tried to decommission. That seemed to do the trick. The namenode-log immediately started printing: 2007-03-27 17:37:19,954 INFO dfs.StateChange - BLOCK* NameSystem.pendingTransfer: ask x.x.x.x:50010 to replicate blk_9167696482646713604 to datanode(s) x.x.x.x:50010 2007-03-27 17:37:19,954 INFO dfs.StateChange - BLOCK* NameSystem.pendingTransfer: ask x.x.x.x:50010 to replicate blk_9168899963250271798 to datanode(s) x.x.x.x:50010 and then finally: 2007-03-28 00:10:41,876 INFO fs.FSNamesystem - Decommission complete for node x.x.x.x:50010
Could it be decommission doesn't work when replication is set to 1? Thanks for your help! - Espen On Tuesday 27 March 2007 18:46:54 Dhruba Borthakur wrote: > I agree. A decommission-meter would be a really helpful tool to monitor the > progress of a decommission command. > > Thanks, > dhruba > > -----Original Message----- > From: Andrzej Bialecki [mailto:[EMAIL PROTECTED] > Sent: Tuesday, March 27, 2007 9:45 AM > To: [email protected] > Subject: Re: Decommission in hadoop-0.12.2 > > Dhruba Borthakur wrote: > > The decommission-in-progress state indicates that the Namenode is > > triggering > > > replication of blocks that reside on the node-being-decommissioned. When > > all > > > those blocks get replicated to another Datanode(s),then the state should > > change to 'decommissioned". > > > > You can run a bin/hdoop fsck -blocks -locations -files to list out all > > the locations of all blocks in the fs (this might take lots of time > > depending > > on > > > the number of files). Please verify if any of the blocks that reside on > > the > > > decommission-in-progress node have 2 replicas. Once all those blocks have > > two replicas (because you have set replication factor to 1), the > > decommissioning should be complete. > > ... though it would be nice if the report gave a "xx% complete" > information ...
