If a CheckpointNode or a BackupNode is used then the SecondaryNameNode should
be disabled.
--Konstantin
On 9/9/2010 7:59 AM, Edward Capriolo wrote:
It is a bad idea to permanently disable 2nn. The edits file grows very
very large and will not be processed until the name node restart. We
had a 12GB edit file that took 40 minutes of downtime to process.
On Thu, Sep 9, 2010 at 3:08 AM, Jeff Zhang<zjf...@gmail.com> wrote:
then, do not start secondary namenode
(
comment the last line of start-dfs.sh
# "$bin"/hadoop-daemons.sh --config $HADOOP_CONF_DIR --hosts masters
start secondarynamenode
)
On Wed, Sep 8, 2010 at 11:36 PM, akhilesh.kumar
<akhilesh.ku...@zapak.co.in> wrote:
Hi ,
Can any one help me in disabling secondary namenode feature of hdfs .
Regards
Akhilesh
-----Original Message-----
From: ChingShen [mailto:chingshenc...@gmail.com]
Sent: Thursday, September 09, 2010 12:07 PM
To: common-user@hadoop.apache.org
Subject: Questions about BN and CN
Hi all,
I got the Backup node(BN) that includes all the checkpoint
responsibilities,
and it maintains an up-to-date namespace state, which is always in
sync with the active NN.
Q1. In which situation do we need a CN?
Q2. If the NameNode machine fails, which different manual
intervention between BN and CN?
Thanks.
Shen
--
Best Regards
Jeff Zhang
