Thanks Harsh,
(1) Thankfully, due to block sizes the latter isn't a problem for large
files on a proper DN, as the blocks are spread over the disks and across
the nodes. -- What do you mean DN?
(2) So, you mean concurrent read for small block will not degrade
performance, but concurrent read for
You need the following:
- active namenode + zkfc
- standby namenode + zkfc
- pool of journal nodes (odd number, 3 or more)
- pool of zookeeper nodes (odd number, 3 or more)
As the journal nodes hold the namesystem transactions they should not be
co-located with the namenodes in case of failure.
OK, I have reliable storage on my datanodes so not an issue for me. If
that's what Cloudera recommends then I'm sure it's fine.
On Dec 28, 2012 10:38 AM, ESGLinux esggru...@gmail.com wrote:
Hi Craig,
I´m a bit confused, I have read this from cloudera:
Answer B sounds pathologically bad to me.
A or C are the only viable options.
Neither B nor D work. B fails because it would be extremely hard to get
the right records to the right components and because it pollutes data
input with configuration data. D fails because statics don't work in
Sounds like someone is cheating on a test...
Sent from a remote device. Please excuse any typos...
Mike Segel
On Dec 28, 2012, at 3:10 PM, Ted Dunning tdunn...@maprtech.com wrote:
Answer B sounds pathologically bad to me.
A or C are the only viable options.
Neither B nor D work. B
the only way to implement B is by doing A (that i know of, at least).
Also, the word each is clearly a dead giveaway that B is the wrong
answer, since it implies special logic for communicating with individual
mappers/reducers.
On Fri, Dec 28, 2012 at 8:20 PM, Edward Capriolo
http://hadoop.apache.org/docs/r1.0.4/hdfs_user_guide.html#Backup+Node
the document write:
The Backup node is configured in the same manner as the Checkpoint node. It
is started with bin/hdfs namenode -checkpoint
but hadoop 1.0.4 there is no hdfs file:
[zhouhh@Hadoop48 hadoop-1.0.4]$ ls bin
ok, retported bug as HDFS-4348https://issues.apache.org/jira/browse/HDFS-4348
.
thanks.
Andy
2012/12/29 Suresh Srinivas sur...@hortonworks.com
This is a documentation bug. Backup node is not available in 1.x release.
It is available in 0.23 and 2.x releases. Please create a bug to point 1.x
Hi,
I'd already addressed this via
https://issues.apache.org/jira/browse/HADOOP-7297 and it isn't present
anymore in 1.1.x+ docs.
On Sat, Dec 29, 2012 at 11:42 AM, 周梦想 abloz...@gmail.com wrote:
ok, retported bug as HDFS-4348.
thanks.
Andy
2012/12/29 Suresh Srinivas sur...@hortonworks.com
