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

Hadoop QA commented on HBASE-9207:
----------------------------------

{color:red}-1 overall{color}.  Here are the results of testing the latest 
attachment 
  http://issues.apache.org/jira/secure/attachment/12598063/0.94-9207_v3.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 6 new 
or modified tests.

    {color:red}-1 patch{color}.  The patch command could not apply the patch.

Console output: 
https://builds.apache.org/job/PreCommit-HBASE-Build/6750//console

This message is automatically generated.
                
> An Offline SplitParent Region can be assigned breaking split references
> -----------------------------------------------------------------------
>
>                 Key: HBASE-9207
>                 URL: https://issues.apache.org/jira/browse/HBASE-9207
>             Project: HBase
>          Issue Type: Bug
>          Components: Region Assignment
>    Affects Versions: 0.98.0, 0.95.1, 0.94.10
>            Reporter: Matteo Bertozzi
>            Assignee: Jimmy Xiang
>             Fix For: 0.94.12
>
>         Attachments: 0.94-9204.patch, 0.94-9204_v2.patch, 0.94-9207_v3.patch
>
>
> An offline split parent region can be assigned by using 'assign' from shell.
> This may trigger a compaction on the split parent region that should be 
> offline, breaking the references of the two daughters.
> The easy way to test this is:
>  * disable compactions
>  * create a table and insert some row
>  * split
>  * shutdown the master (otherwise there's a state checked inside the 
> AssignmentManager)
>  * start the master
>  * assign the region marked as OFFLINE => true, SPLIT => true (the compaction 
> on region startup will probably break the reference of the two  daughters)

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