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.hosts.exclude} settings in the namenode's hdfs-site.xml.
The namenode doesn't actually care about the slaves file. It's only
used by the start/stop scripts.
On 2012/03/02 10:35, Mohit Anchlia wrote:
I actually meant to ask how does namenode/jobtracker know there is a new
node in the cluster. Is it initiated by namenode when slave file is edited?
Or is it initiated by tasktracker when tasktracker is started?
