Usually for reliability there will be multiple dfs.name.dir configured. Of which one would be a remote location such as a nfs mount.
So that even if the NN machine crashes on a whole you still have the fs image and edit log in nfs mount. This can be utilized for reconstructing the NN back again.
Sent from remote device, Please excuse typos
From: Panshul Whisper <[EMAIL PROTECTED]>
Date: Mon, 14 Jan 2013 17:25:08
To: <[EMAIL PROTECTED]>
Reply-To: [EMAIL PROTECTED]
Subject: hadoop namenode recovery
Is there a standard way to prevent the failure of Namenode crash in a
or what is the standard or best practice for overcoming the Single point
failure problem of Hadoop.
I am not ready to take chances on a production server with Hadoop 2.0 Alpha
release, which claims to have solved the problem. Are there any other
things I can do to either prevent the failure or recover from the failure
in a very short time.