tag:blogger.com,1999:blog-8716531089719420013.post6145618455788189201..comments2024-01-15T11:45:52.649+05:30Comments on Big Data and Cloud Tips: WhatsWrong : DataNode on remote machine not able to connect to NameNodePraveen Sripatihttp://www.blogger.com/profile/11782284194201977787noreply@blogger.comBlogger8125tag:blogger.com,1999:blog-8716531089719420013.post-16918675012325010702013-02-06T23:08:50.210+05:302013-02-06T23:08:50.210+05:30Thanks Praveen, this helped finally get my hadoop ...Thanks Praveen, this helped finally get my hadoop cluster up and runningAnonymoushttps://www.blogger.com/profile/08566543624751657240noreply@blogger.comtag:blogger.com,1999:blog-8716531089719420013.post-718899392582568252013-02-06T18:32:55.032+05:302013-02-06T18:32:55.032+05:30Chris,
The same would be applicable for the mapre...Chris,<br /><br />The same would be applicable for the mapred-site.xml also. If localhost:9001 is mentioned in the configuration file, then the remote tasktracker won't be able to talk to the jobtracker.<br /><br />PraveenPraveen Sripatihttps://www.blogger.com/profile/11782284194201977787noreply@blogger.comtag:blogger.com,1999:blog-8716531089719420013.post-2812082591882621122013-02-06T18:11:37.747+05:302013-02-06T18:11:37.747+05:30Hi, would this also be the case for the mapred-sit...Hi, would this also be the case for the mapred-site.xml. That is, would putting localhost:9001 in the mapred-site.xml also cause bind problems for a datanode trying to connect to the namenode?<br /><br />Anonymoushttps://www.blogger.com/profile/08566543624751657240noreply@blogger.comtag:blogger.com,1999:blog-8716531089719420013.post-89357125541886051022012-07-05T07:07:12.722+05:302012-07-05T07:07:12.722+05:30Yes, i replaced and it worked, thank youYes, i replaced and it worked, thank yousrikanth ayalasomayajuluhttps://www.blogger.com/profile/12648091832726495905noreply@blogger.comtag:blogger.com,1999:blog-8716531089719420013.post-56929852303822900812012-07-04T11:52:08.220+05:302012-07-04T11:52:08.220+05:30> i set fs.default.name to localhost on namenod...> i set fs.default.name to localhost on namenode<br /><br />Set it to hostname/ip as mentioned in the first comment instead of the localhost.Praveen Sripatihttps://www.blogger.com/profile/11782284194201977787noreply@blogger.comtag:blogger.com,1999:blog-8716531089719420013.post-90724771419381674832012-07-04T10:33:54.551+05:302012-07-04T10:33:54.551+05:30i tried to setup a cluster , with namenode on one ...i tried to setup a cluster , with namenode on one node, 3 datanodes and i set fs.default.name to localhost on namenode and master ip address on datanodes. but i am getting the same error. can anyone please help me.srikanth ayalasomayajuluhttps://www.blogger.com/profile/12648091832726495905noreply@blogger.comtag:blogger.com,1999:blog-8716531089719420013.post-61048600960333202112012-02-01T17:32:41.714+05:302012-02-01T17:32:41.714+05:30As to why, the source code looks like the followin...As to why, the source code looks like the following for fs.default.name set to localhost<br /><br /> ServerSocket socket = new ServerSocket(9000);<br /> socket.bind(localhost);<br /><br />Because bind address is assigned to localhost, the namenode process only can accept connection from localhost. If bind address is assigned to the name of machine name or ip address, then namenode process can accept any connection from remote machine.Praveen Sripatihttps://www.blogger.com/profile/11782284194201977787noreply@blogger.comtag:blogger.com,1999:blog-8716531089719420013.post-78173906112236978392012-02-01T16:34:53.191+05:302012-02-01T16:34:53.191+05:30I think fs.default.name should point to node1 ip a...I think fs.default.name should point to node1 ip address instaed of localhost.mrkhttps://www.blogger.com/profile/01745463952687281903noreply@blogger.com