-user@hadoop.apache.org
Subject: Re: Setting up another machine as secondary node
Hey Koji,
It's an expensive operation - for the secondary namenode, not the
namenode itself, right? I don't particularly care if I stress out a
dedicated node that doesn't have to respond to queries ;)
Locally we
, May 14, 2009 10:32 AM
To: core-user@hadoop.apache.org
Subject: Re: Setting up another machine as secondary node
Hey Koji,
It's an expensive operation - for the secondary namenode, not the
namenode itself, right? I don't particularly care if I stress out a
dedicated node that doesn't have to respond
...@cse.unl.edu]
Sent: Thursday, May 14, 2009 10:32 AM
To: core-user@hadoop.apache.org
Subject: Re: Setting up another machine as secondary node
Hey Koji,
It's an expensive operation - for the secondary namenode, not the
namenode itself, right? I don't particularly care if I stress out
help after 0.19 or later.
Koji
-Original Message-
From: Brian Bockelman [mailto:bbock...@cse.unl.edu]
Sent: Thursday, May 14, 2009 10:32 AM
To: core-user@hadoop.apache.org
Subject: Re: Setting up another machine as secondary node
Hey Koji,
It's an expensive operation - for the secondary
Message-
From: Brian Bockelman [mailto:bbock...@cse.unl.edu]
Sent: Thursday, May 14, 2009 10:32 AM
To: core-user@hadoop.apache.org
Subject: Re: Setting up another machine as secondary node
Hey Koji,
It's an expensive operation - for the secondary namenode, not the
namenode itself, right
Hi,
I wanna set up a cluster of 5 nodes in such a way that
node1 - master
node2 - secondary namenode
node3 - slave
node4 - slave
node5 - slave
How do we go about that?
there is no property in hadoop-env where i can set the ip-address for
secondary name node.
if i set node-1 and node-2 in
First of all, the secondary namenode is not a what you might think a
secondary is - it's not failover device. It does make a copy of the
filesystem metadata periodically, and it integrates the edits into the
image. It does *not* provide failover.
Second, you specify its IP address in
any machine put in the conf/masters file becomes a secondary namenode.
At some point there was confusion on the safety of more than one machine,
which I believe was settled, as many are safe.
The secondary namenode takes a snapshot at 5 minute (configurable)
intervals, rebuilds the fsimage and
[mailto:jason.had...@gmail.com]
Sent: Thursday, May 14, 2009 7:46 AM
To: core-user@hadoop.apache.org
Subject: Re: Setting up another machine as secondary node
any machine put in the conf/masters file becomes a secondary namenode.
At some point there was confusion on the safety of more than one
machine,
which I
or even every day.
Isn't the default 3600 seconds?
Koji
-Original Message-
From: jason hadoop [mailto:jason.had...@gmail.com]
Sent: Thursday, May 14, 2009 7:46 AM
To: core-user@hadoop.apache.org
Subject: Re: Setting up another machine as secondary node
any machine put in the conf/masters
0.19 or later.
Koji
-Original Message-
From: Brian Bockelman [mailto:bbock...@cse.unl.edu]
Sent: Thursday, May 14, 2009 10:32 AM
To: core-user@hadoop.apache.org
Subject: Re: Setting up another machine as secondary node
Hey Koji,
It's an expensive operation - for the secondary namenode
11 matches
Mail list logo