What if there is no region information in NSRE ? 2010-04-08 10:26:38,385 ERROR [IPC Server handler 60 on 60020] regionserver.HRegionServer(846): Failed openScanner org.apache.hadoop.hbase.NotServingRegionException: domaincrawltable,,1270600690648 at org.apache.hadoop.hbase.regionserver.HRegionServer.getRegion(HRegionServer.java:2307) at org.apache.hadoop.hbase.regionserver.HRegionServer.openScanner(HRegionServer.java:1893) at sun.reflect.GeneratedMethodAccessor8.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:648) at org.apache.hadoop.hbase.ipc.HBaseServer$Handler.run(HBaseServer.java:915)
On Thu, Apr 8, 2010 at 9:39 AM, Jean-Daniel Cryans <jdcry...@apache.org>wrote: > On Wed, Apr 7, 2010 at 11:38 PM, Al Lias <al.l...@gmx.de> wrote: > > Occationally my HTable clients get a response that no server is serving > > a particular region... > > Normally, the region is back a few seconds later (perhaps a split?). > > Or the region moved. > > > > > Anyway, the client (Using HTablePool) seems to need a restart to forget > > this. > > Seems wrong, would love a stack trace. > > > > > Is there a config value to manipulate the caching time of regionserver > > assignments in the client? > > Nope, when the client sees a NSRE, it queries .META. to find the new > location. > > > > > I set a small value for hbase.client.pause to get failures fast. I am > > using 0.20.3 . > > Splits are still kinda slow, takes at least 2 seconds to happen, but > finding the new location of a region is a core feature in HBase and > it's rather well tested, Can you pin down your exact problem? Next > time a NSRE happens, see which region it was looking for and grep the > master log for it, you should see the history and how much time it > took to move. > > > > > Thx, > > > > Al > > >