Hadoop has some weird DNS/Reverse DNS lookup requirements. My guess would be that Hadoop is bonking.
Sent from my iPhone On Sep 23, 2012, at 11:07 AM, Kristopher Kane <[email protected]> wrote: > I left some parts out: > > This is 1.4 and the GC process for fille collection has been running > since the cluster turned on. So, does that mean things are being held > up in the WA logs? > > -KRis > > On Sun, Sep 23, 2012 at 10:50 AM, Kristopher Kane <[email protected]> > wrote: >> All, >> >> I was doing some shuffling around at home and changed IPs on my master >> and all tservers. I thought this would be OK as I had configured >> everything via hostnames but I've got some log entries that say >> otherwise: >> >> >> Unable to recover >> 192.168.122.222:11224/d41fc0de-f4bc-4c28-a4ae-a0114c5911d7(java.io.IOException: >> org.apache.thrift.transport.TTransportException: >> java.net.ConnectException: Connection timed out) >> java.io.IOException: org.apache.thrift.transport.TTransportException: >> java.net.ConnectException: Connection timed out >> >> >> >> This is the master reporting on two tservers of the four I have. Also >> to note: I did have an unclean shutdown prior to the IP changes and >> the monitor shows no tablets loaded for any table with the recovery >> directory in HDFS empty. >> I don't need the data and I can always init, but I was curious about >> fixing this to learn more about the system. >> >> Where is a good place to start? >> >> Thanks, >> >> >> -Kris Kane
