Mohit,
New datanodes will connect to the namenode so thats how the namenode
knows. Just make sure the datanodes have the correct {fs.default.dir}
in their hdfs-site.xml and then start them. The namenode can, however,
choose to reject the datanode if you are using the {dfs.hosts} and
{dfs.ho
Koji, Harsh
mapred-478 seems to be in v1, but those new settings have not yet been
added to mapred-default.xml. (for backwards compatibility?)
George
On 2012/01/12 13:50, Koji Noguchi wrote:
Hi Harsh,
Wasn't MAPREDUCE-478 in 1.0 ? Maybe the Jira is not up to date.
Koji
On 1/11/12 8:44
Is there an Apache Hadoop policy towards maintenance/support of older
Hadoop versions? It seems like 0.20.20* (now 1.0), 0.22, and 0.23 are
the currently active branches. Regarding versions like 0.18 and 0.19,
is there some policy like "up to N years" or "up to M releases prior"
where legacy
Nitin,
On 2011/07/28 14:51, Nitin Khandelwal wrote:
How can I determine if a file is being written to (by any thread) in HDFS.
That information is exposed by the NameNode http servlet. You can
obtain it with the
fsck tool (hadoop fsck /path/to/dir -openforwrite) or you can do an http get
htt
Hello
On 2011/01/14 10:02, Mark Kerzner wrote:
hadoop fs -ls hdfs://master-url/
works locally on the master, but cannot connect from any of the slaves.
Make sure to replicate conf/core-site.xml to each of the slaves. The
fs.default.name property should point to the master node. That way th
