hadoop-common-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hadoop QA (JIRA)" <j...@apache.org>
Subject [jira] Commented: (HADOOP-2017) [hbase] TestRegionServerAbort failure in patch build #903 and nightly #266
Date Tue, 09 Oct 2007 21:21:51 GMT

    [ https://issues.apache.org/jira/browse/HADOOP-2017?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12533514

Hadoop QA commented on HADOOP-2017:

+1 overall.  Here are the results of testing the latest attachment 
against trunk revision r583037.

    @author +1.  The patch does not contain any @author tags.

    javadoc +1.  The javadoc tool did not generate any warning messages.

    javac +1.  The applied patch does not generate any new compiler warnings.

    findbugs +1.  The patch does not introduce any new Findbugs warnings.

    core tests +1.  The patch passed core unit tests.

    contrib tests +1.  The patch passed contrib unit tests.

Test results: http://lucene.zones.apache.org:8080/hudson/job/Hadoop-Patch/910/testReport/
Findbugs warnings: http://lucene.zones.apache.org:8080/hudson/job/Hadoop-Patch/910/artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html
Checkstyle results: http://lucene.zones.apache.org:8080/hudson/job/Hadoop-Patch/910/artifact/trunk/build/test/checkstyle-errors.html
Console output: http://lucene.zones.apache.org:8080/hudson/job/Hadoop-Patch/910/console

This message is automatically generated.

> [hbase] TestRegionServerAbort failure in patch build #903 and nightly #266
> --------------------------------------------------------------------------
>                 Key: HADOOP-2017
>                 URL: https://issues.apache.org/jira/browse/HADOOP-2017
>             Project: Hadoop
>          Issue Type: Bug
>          Components: contrib/hbase
>            Reporter: stack
>            Priority: Minor
>             Fix For: 0.15.0
>         Attachments: trsa.patch
> In patch build #903, the metascanner keeps trying to go to the downed server even though
onlineMetaRegions has been updated w/ new location and then the metascanner just goes away
(or hangs).
> In nightly build #266, its a similar scenario only the remaining region servers decide
to shut down because they haven't been able to reach the master in 7 seconds.

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message