Ugly IOE when region is being closed; rather, should NSRE
---------------------------------------------------------
Key: HBASE-2516
URL: https://issues.apache.org/jira/browse/HBASE-2516
Project: Hadoop HBase
Issue Type: Bug
Reporter: stack
Fix For: 0.20.5, 0.21.0
I'm running 80/20 YCSB (80% reads/20% writes). I see this from time to time in
logs (especially if I do big fat bulk upload at same time -- having trouble
making ycsb do heavy loading at mo):
{code}
2010-05-05 06:57:01,165 DEBUG org.apache.hadoop.hbase.regionserver.HRegion:
Updates disabled for region, no outstanding scanners on
usertable,user1431413702,1273040674721
2010-05-05 06:57:01,165 DEBUG org.apache.hadoop.hbase.regionserver.HRegion: No
more row locks outstanding on region usertable,user1431413702,1273040674721
2010-05-05 06:57:01,178 DEBUG org.apache.hadoop.hbase.regionserver.Store:
closed cf
2010-05-05 06:57:01,178 INFO org.apache.hadoop.hbase.regionserver.HRegion:
Closed usertable,user1431413702,1273040674721
2010-05-05 06:57:01,178 ERROR
org.apache.hadoop.hbase.regionserver.HRegionServer:
java.io.IOException: Region usertable,user1431413702,1273040674721 closed
at
org.apache.hadoop.hbase.regionserver.HRegion.getScanner(HRegion.java:1179)
at
org.apache.hadoop.hbase.regionserver.HRegion.getScanner(HRegion.java:1172)
at org.apache.hadoop.hbase.regionserver.HRegion.get(HRegion.java:2506)
at org.apache.hadoop.hbase.regionserver.HRegion.get(HRegion.java:2493)
at
org.apache.hadoop.hbase.regionserver.HRegionServer.get(HRegionServer.java:1742)
at sun.reflect.GeneratedMethodAccessor12.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:657)
at
org.apache.hadoop.hbase.ipc.HBaseServer$Handler.run(HBaseServer.java:915)
{code}
This should be a NSRE.
J-D took a look and fact that we do an IOE 'region closed' is way old, from
before the time forgot, so its just always been there just more obvious now
that Get is a Scan.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
