[
https://issues.apache.org/jira/browse/HBASE-7681?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13563564#comment-13563564
]
Ted Yu commented on HBASE-7681:
-------------------------------
>From
>https://builds.apache.org/job/HBase-0.94/776/testReport/junit/org.apache.hadoop.hbase.coprocessor/TestRegionServerCoprocessorExceptionWithAbort/testExceptionFromCoprocessorDuringPut/
> :
{code}
013-01-26 01:03:43,509 ERROR
[RS_OPEN_REGION-juno.apache.org,41700,1359162211501-1]
coprocessor.CoprocessorHost$Environment(657): Error starting coprocessor
org.apache.hadoop.hbase.coprocessor.TestRegionServerCoprocessorExceptionWithAbort$BuggyRegionObserver
org.apache.hadoop.hbase.regionserver.WrongRegionException: Requested row out of
range for row lock on HRegion
observed_table,,1359162223098.d367ba98501279646d44c0c1530fb6c4., startKey='',
getEndKey()='bbb', row='some row'
at
org.apache.hadoop.hbase.regionserver.HRegion.checkRow(HRegion.java:3191)
at
org.apache.hadoop.hbase.regionserver.HRegion.internalObtainRowLock(HRegion.java:3240)
at
org.apache.hadoop.hbase.regionserver.HRegion.getLock(HRegion.java:3336)
at
org.apache.hadoop.hbase.coprocessor.SimpleRegionObserver.start(SimpleRegionObserver.java:110)
at
org.apache.hadoop.hbase.coprocessor.CoprocessorHost$Environment.startup(CoprocessorHost.java:654)
at
org.apache.hadoop.hbase.coprocessor.CoprocessorHost.loadInstance(CoprocessorHost.java:312)
at
org.apache.hadoop.hbase.coprocessor.CoprocessorHost.loadSystemCoprocessors(CoprocessorHost.java:149)
at
org.apache.hadoop.hbase.regionserver.RegionCoprocessorHost.<init>(RegionCoprocessorHost.java:144)
at org.apache.hadoop.hbase.regionserver.HRegion.<init>(HRegion.java:464)
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at
sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)
at
sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
at java.lang.reflect.Constructor.newInstance(Constructor.java:513)
at
org.apache.hadoop.hbase.regionserver.HRegion.newHRegion(HRegion.java:3937)
at
org.apache.hadoop.hbase.regionserver.HRegion.openHRegion(HRegion.java:4118)
at
org.apache.hadoop.hbase.regionserver.handler.OpenRegionHandler.openRegion(OpenRegionHandler.java:332)
at
org.apache.hadoop.hbase.regionserver.handler.OpenRegionHandler.process(OpenRegionHandler.java:108)
at
org.apache.hadoop.hbase.executor.EventHandler.run(EventHandler.java:169)
{code}
SimpleRegionObserver is inherited by BuggyRegionObserver. If coprocessor cannot
start, this test wouldn't succeed.
Here is SimpleRegionObserver#start():
{code}
public void start(CoprocessorEnvironment e) throws IOException {
// this only makes sure that leases and locks are available to coprocessors
...
Integer lid = re.getRegion().getLock(null, Bytes.toBytes("some row"), true);
re.getRegion().releaseRowLock(lid);
{code}
We should at least wrap the call to getLock() with try/catch.
> Increase timeouts in some more test...?
> ---------------------------------------
>
> Key: HBASE-7681
> URL: https://issues.apache.org/jira/browse/HBASE-7681
> Project: HBase
> Issue Type: Bug
> Reporter: Lars Hofhansl
> Fix For: 0.94.5
>
> Attachments: 7681-0.94.txt
>
>
> I've seen many unspecific test failures recently that cannot be reproduced
> locally even when running these test is a loop for a very long time.
> Many of these test one way or the other make assumption w.r.t. wall clock
> time. While I cannot fix that, an option to increase some of these timeout a
> bit.
> This issue is to remind me to do that.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
