Michael, This is normal when not followed by RetriesExhausted exceptions. That exception is used by the region servers to tell the clients that a certain region was moved (because of rebalancing or splitting) and that they should refresh their cache.
J-D On Wed, Mar 18, 2009 at 4:00 AM, Michael Dagaev <[email protected]> wrote: > Hi all > > We run a small Hbase 0.18 cluster (4 machines). > A few days ago the traffic (mostly writes) increased > and we started to notice NotServingRegionExceptions. > > Has anybody run into such a problem ? > > org.apache.hadoop.hbase.NotServingRegionException: Region <...> closed > at > org.apache.hadoop.hbase.regionserver.HRegion.obtainRowLock(HRegion.java:1810) > at > org.apache.hadoop.hbase.regionserver.HRegion.getLock(HRegion.java:1875) > at > org.apache.hadoop.hbase.regionserver.HRegion.batchUpdate(HRegion.java:1406) > at > org.apache.hadoop.hbase.regionserver.HRegion.batchUpdate(HRegion.java:1380) > at > org.apache.hadoop.hbase.regionserver.HRegionServer.batchUpdate(HRegionServer.java:1114) > at sun.reflect.GeneratedMethodAccessor5.invoke(Unknown Source) > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) > at java.lang.reflect.Method.invoke(Method.java:597) > at org.apache.hadoop.hbase.ipc.HbaseRPC$Server.call(HbaseRPC.java:554) > at org.apache.hadoop.ipc.Server$Handler.run(Server.java:888) > > Thank you for your cooperation, > M. > > P.S. Yes, we are going to upgrade our cluster to Hbase 0.19 >
