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-2417) [hbase] Fix critical shutdown problem introduced by HADOOP-2338
Date Thu, 13 Dec 2007 20:01:19 GMT

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

Hadoop QA commented on HADOOP-2417:

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

    @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/1338/testReport/
Findbugs warnings: http://lucene.zones.apache.org:8080/hudson/job/Hadoop-Patch/1338/artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html
Checkstyle results: http://lucene.zones.apache.org:8080/hudson/job/Hadoop-Patch/1338/artifact/trunk/build/test/checkstyle-errors.html
Console output: http://lucene.zones.apache.org:8080/hudson/job/Hadoop-Patch/1338/console

This message is automatically generated.

> [hbase] Fix critical shutdown problem introduced by HADOOP-2338
> ---------------------------------------------------------------
>                 Key: HADOOP-2417
>                 URL: https://issues.apache.org/jira/browse/HADOOP-2417
>             Project: Hadoop
>          Issue Type: Bug
>          Components: contrib/hbase
>    Affects Versions: 0.16.0
>            Reporter: Jim Kellerman
>            Assignee: Jim Kellerman
>            Priority: Critical
>             Fix For: 0.16.0
>         Attachments: patch.txt
> HADOOP-1338 introduced a critical problem in region server shutdown.
> - when a region server is told by the master to quiesce, closing a region can cause a
concurrent split to fail, possibly corrupting the region.
> In addition, the master may never transition from quiesce to full shutdown, leaving some
region servers still running in quiesce state.

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

View raw message