Hi, You can have this if the region moved, i.e. was previously managed by this region server and is now managed by another. The client keeps a cache of the locations, so after a move it will first contact the wrong server. Then the client will update its cache. By default there are 10 internal retries so the next retry will be the right one, and this error should not be seen in the customer code.
In 0.96 the regions server will send back a RegionMovedException with the new location if the move is not too old (less than around ~5 minutes if I remember well). N. On Thu, Jun 7, 2012 at 9:36 PM, arun sirimalla <arunsi...@gmail.com> wrote: > Hi, > > My Hbase cluster seems to work fine, but i see some exepctions in one of > the RegionServer with below message > > 2012-06-07 19:24:48,809 DEBUG > org.apache.hadoop.hbase.regionserver.HRegionServer: > NotServingRegionException; Region is not online: -ROOT-,,0 > 2012-06-07 19:24:56,154 DEBUG > org.apache.hadoop.hbase.regionserver.HRegionServer: > NotServingRegionException; Region is not online: -ROOT-,,0 > > Though this regionserver is not Hosting the ROOT region. The -ROOT- region > is hosted by another Regionserver. Can someone please tell me why these > exceptions occur. > > Thanks > Arun
