login your remote datanode and start the datanode manually to see what happen.
start HDFS based on the WAN is not as easy as on a cluster. There are many issues. datanode log should be the best way to shoot troubles. Chen On Fri, Mar 30, 2012 at 12:52 PM, Michael Segel <michael_se...@hotmail.com>wrote: > Probably a timeout. > Really, not a good idea to do this in the first place... > > Sent from my iPhone > > On Mar 30, 2012, at 12:35 PM, "Ben Cuthbert" <bencuthb...@ymail.com> > wrote: > > > Strange thing is the datanode in the remote location has a log zero > bytes. So nothing there. > > Its strange it is like the master does and ssh, login, and then attempts > to start it but nothing. Maybe there is a timeout? > > > > > > On 30 Mar 2012, at 18:22, kasi subrahmanyam wrote: > > > >> Try checking the logs in the logs folder for the datanode.It might give > >> some lead. > >> Maybe there is a mismatch between the namespace iDs in the system and > user > >> itself while starting the datanode. > >> > >> On Fri, Mar 30, 2012 at 10:32 PM, Ben Cuthbert <bencuthb...@ymail.com > >wrote: > >> > >>> All > >>> > >>> We have a master in one region and we are trying to start a slave > datanode > >>> in another region. When executing the scripts it looks to login to the > >>> remote host, but > >>> never starts the datanode. When executing hbase tho it does work. Is > there > >>> a timeout or something with hadoop? > > >
