hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "stack (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-16725) Don't let flushThread hang in TestHRegion
Date Thu, 29 Sep 2016 05:13:20 GMT

    [ https://issues.apache.org/jira/browse/HBASE-16725?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15531815#comment-15531815
] 

stack commented on HBASE-16725:
-------------------------------

+1

I don't see how the failures are related given a patch for a test. Are the failing tests subclassing
or reusing this part of TestHRegion?



> Don't let flushThread hang in TestHRegion
> -----------------------------------------
>
>                 Key: HBASE-16725
>                 URL: https://issues.apache.org/jira/browse/HBASE-16725
>             Project: HBase
>          Issue Type: Test
>            Reporter: Ted Yu
>            Assignee: Ted Yu
>            Priority: Minor
>         Attachments: 16725.branch-1.v1.txt, 16725.branch-1.v2.txt, 16725.v2.txt
>
>
> I was running TestHRegion locally and observed the following in test output:
> {code}
> 2016-09-28 16:29:36,836 INFO  [main] hbase.ResourceChecker(171): after: regionserver.TestHRegion#testFlushCacheWhileScanning
Thread=50 (was 49)
> Potentially hanging thread: FlushThread
>   java.lang.Object.wait(Native Method)
>   java.lang.Object.wait(Object.java:502)
>   org.apache.hadoop.hbase.regionserver.TestHRegion$FlushThread.run(TestHRegion.java:3834)
> {code}
> Call to flushThread.done() etc should be placed in the finally block.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message