I wish I had read the bug more carefully - thought that the issue was fixed in 0.13.1.
Of course not, the issue persists. Meanwhile - half the files are corrupted after the upgrade (followed the upgrade wiki, tried to restore to backed up metadata and old version - to no avail). Sigh - have a nice weekend everyone, Joydeep -----Original Message----- From: Koji Noguchi [mailto:[EMAIL PROTECTED] Sent: Friday, August 24, 2007 8:29 AM To: [email protected] Subject: Re: secondary namenode errors Joydeep, I think you're hitting this bug. http://issues.apache.org/jira/browse/HADOOP-1076 In any case, as Raghu suggested, please use 0.13.1 and not 0.13. Koji Raghu Angadi wrote: > Joydeep Sen Sarma wrote: >> Thanks for replying. >> >> Can you please clarify - is it the case that the secondary namenode >> stuff only works in 0.13.1? and what's the connection with replication >> factor? >> >> We lost the file system completely once, trying to make sure we can >> avoid it the next time. > > I am not sure if the problem you reported still exists in 0.13.1. You > might still have the problem and you can ask again. But you should > move to 0.13.1 since it has some critical fixes. See release notes for > 0.13.1 or HADOOP-1603. You should always upgrade to the latest minor > release version when moving to next major version. > > Raghu. > >> Joydeep >> >> -----Original Message----- >> From: Raghu Angadi [mailto:[EMAIL PROTECTED] Sent: Thursday, >> August 23, 2007 9:44 PM >> To: [email protected] >> Subject: Re: secondary namenode errors >> >> >> On a related note, please don't use 0.13.0, use the latest released >> version for 0.13 (I think it is 0.13.1). If the secondary namenode >> actually works, then it will resulting all the replications set to 1. >> >> Raghu. >> >> Joydeep Sen Sarma wrote: >>> Hi folks,
