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

Hadoop QA commented on HBASE-6258:
----------------------------------

-1 overall.  Here are the results of testing the latest attachment 
  
http://issues.apache.org/jira/secure/attachment/12533075/HBASE-4816%2B4881%2B5189%2B6158.patch
  against trunk revision .

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

    -1 tests included.  The patch doesn't appear to include any new or modified 
tests.
                        Please justify why no new tests are needed for this 
patch.
                        Also please list what manual steps were performed to 
verify this patch.

    -1 patch.  The patch command could not apply the patch.

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

This message is automatically generated.
                
> Backport some region splitting fixes into 0.90.7
> ------------------------------------------------
>
>                 Key: HBASE-6258
>                 URL: https://issues.apache.org/jira/browse/HBASE-6258
>             Project: HBase
>          Issue Type: Bug
>          Components: regionserver
>    Affects Versions: 0.90.6
>            Reporter: David S. Wang
>            Assignee: David S. Wang
>         Attachments: HBASE-4816+4881+5189+6158.patch
>
>
> Issue tracking backport of some relatively small region splitting fixes into 
> 0.90.7:
> HBASE-4816: Regionserver wouldn't go down because split happened exactly at 
> same time we issued bulk user region close call on our way out - fixed in 0.92
> HBASE-4881: Unhealthy region is on service caused by rollback of region 
> splitting - fixed in 0.92
> HBASE-5189: Add metrics to keep track of region-splits in RS - fixed in 0.94
> HBASE-6158: Data loss if the words 'merges' or 'splits' are used as Column 
> Family name - fixed in 0.92 and 0.94

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

        

Reply via email to