Yeah that null message isn't really helpful :) So one thing that might be helpful would be to know who DC1AuthDFSC1D3 is, since you identified the logs as "Region server n".
Then look at the master's web UI and see where -ROOT- is assigned. Is it also DC1AuthDFSC1D3? If so, then I would proceed by checking if there's a firewall in between the client and the cluster, also I would make sure that the client is running the same version as the server. J-D On Sat, Aug 20, 2011 at 5:56 AM, Srikanth P. Shreenivas <[email protected]> wrote: > Further in this investigation, we enabled the debug logs on client side. > > We are observing that client is trying to root region, and is continuously > failing to do so. The logs are filled with entries like this: > > 2011-08-20 17:20:09,092 [gridgain-#6%authGrid%] DEBUG > [hbase.client.HConnectionManager$HConnectionImplementation] - Lookedup root > region location, > connection=org.apache.hadoop.hbase.client.HConnectionManager$HConnectionImplementation@2cc25ae3; > hsa=DC1AuthDFSC1D3.cidr.gov.in:6020 > 2011-08-20 17:20:09,092 [gridgain-#6%authGrid%] DEBUG > [hbase.client.HConnectionManager$HConnectionImplementation] - > locateRegionInMeta parentTable=-ROOT-, metaLocation=address: > DC1AuthDFSC1D3.cidr.gov.in:6020, regioninfo: -ROOT-,,0.70236052, attempt=0 of > 10 failed; retrying after sleep of 1000 > because: null > > Client keeps retrying and retries get exhausted. > > > Complete logs are available here: https://gist.github.com/1159064 including > logs of master, zookeeper and region servers. > > > If you can please look at the logs and provide some inputs on this issue, > then it will be really helpful. > We are really not sure why client is failing to get root regions from the > server. Any guidance will be greatly appreciated. > > > Thanks a lot, > Srikanth
