hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "stack (Commented) (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-4690) Intermittent TestRegionServerCoprocessorExceptionWithRemove#testExceptionFromCoprocessorDuringPut failure
Date Fri, 28 Oct 2011 04:42:34 GMT

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

stack commented on HBASE-4690:
------------------------------

I added debug so next time it fails on jenkins, hopefully a bit more info.

There are two tests named TestRegionServerCoprocessor* that have the same form that each spin
up a cluster to do one thing (We should consider putting them together).  Both seem to fail
here checking for first region.  I tried to take a look at it and it doesn't make sense. 
Just before the outofbounds we've checked the list is not empty.

Lets see if the debugging added helps. 
                
> Intermittent TestRegionServerCoprocessorExceptionWithRemove#testExceptionFromCoprocessorDuringPut
failure
> ---------------------------------------------------------------------------------------------------------
>
>                 Key: HBASE-4690
>                 URL: https://issues.apache.org/jira/browse/HBASE-4690
>             Project: HBase
>          Issue Type: Test
>    Affects Versions: 0.92.0
>            Reporter: Ted Yu
>            Assignee: Eugene Koontz
>             Fix For: 0.92.0
>
>
> See https://builds.apache.org/view/G-L/view/HBase/job/HBase-0.92/83/testReport/junit/org.apache.hadoop.hbase.coprocessor/TestRegionServerCoprocessorExceptionWithAbort/testExceptionFromCoprocessorDuringPut/
> Somehow getRSForFirstRegionInTable() wasn't able to retrieve the region server.
> One fix for this issue is to spin up MiniCluster with 1 region server so that we don't
need to search for the region server where first region is hosted.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message