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

Hadoop QA commented on HBASE-9233:
----------------------------------

{color:green}+1 overall{color}.  Here are the results of testing the latest 
attachment 
  
http://issues.apache.org/jira/secure/attachment/12598401/HBASE-9233-trunk-v1.patch
  against trunk revision .

    {color:green}+1 @author{color}.  The patch does not contain any @author 
tags.

    {color:green}+1 tests included{color}.  The patch appears to include 3 new 
or modified tests.

    {color:green}+1 hadoop1.0{color}.  The patch compiles against the hadoop 
1.0 profile.

    {color:green}+1 hadoop2.0{color}.  The patch compiles against the hadoop 
2.0 profile.

    {color:green}+1 javadoc{color}.  The javadoc tool did not generate any 
warning messages.

    {color:green}+1 javac{color}.  The applied patch does not increase the 
total number of javac compiler warnings.

    {color:green}+1 findbugs{color}.  The patch does not introduce any new 
Findbugs (version 1.3.9) warnings.

    {color:green}+1 release audit{color}.  The applied patch does not increase 
the total number of release audit warnings.

    {color:green}+1 lineLengths{color}.  The patch does not introduce lines 
longer than 100

  {color:green}+1 site{color}.  The mvn site goal succeeds with this patch.

    {color:green}+1 core tests{color}.  The patch passed unit tests in .

Test results: 
https://builds.apache.org/job/PreCommit-HBASE-Build/6790//testReport/
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-HBASE-Build/6790//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-protocol.html
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-HBASE-Build/6790//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-client.html
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-HBASE-Build/6790//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-examples.html
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-HBASE-Build/6790//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-hadoop1-compat.html
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-HBASE-Build/6790//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-prefix-tree.html
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-HBASE-Build/6790//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-common.html
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-HBASE-Build/6790//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-server.html
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-HBASE-Build/6790//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-hadoop-compat.html
Console output: 
https://builds.apache.org/job/PreCommit-HBASE-Build/6790//console

This message is automatically generated.
                
> isTableAvailable() may be stuck if an offline parent was never assigned
> -----------------------------------------------------------------------
>
>                 Key: HBASE-9233
>                 URL: https://issues.apache.org/jira/browse/HBASE-9233
>             Project: HBase
>          Issue Type: Bug
>          Components: Client, Region Assignment
>    Affects Versions: 0.98.0, 0.95.1, 0.94.10
>            Reporter: Matteo Bertozzi
>            Assignee: Matteo Bertozzi
>            Priority: Critical
>             Fix For: 0.98.0, 0.94.12, 0.96.0
>
>         Attachments: HBASE-9233-0.94-v0.patch, HBASE-9233-trunk-v0.patch, 
> HBASE-9233-trunk-v1.patch
>
>
> HConnectionManager.isTableAvailable() the SERVER_QUALIFIER for each region, 
> including the offline split parent.
> In case of hbck META recovery or snapshots clone/restore an offline parent 
> will never be assigned (since should stay offline). In this case 
> HBaseAdmin.waitUntilTableIsEnabled() used by enable() and cloneSnapshot() 
> will wait until the timeout is expired.

--
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

Reply via email to