[
https://issues.apache.org/jira/browse/HBASE-7681?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13563580#comment-13563580
]
Lars Hofhansl commented on HBASE-7681:
--------------------------------------
Interesting. So that is only failing when we load that coprocessor into a
region which has a non-empty start key > "some row" or a non-empty end key <
"some row".
I added that part to SimpleRegionObserver. We should just remove it. It is just
making sure that nobody makes HRegion.getLock(...) private again.
> 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
