[
https://issues.apache.org/jira/browse/HADOOP-2451?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12552638
]
Hadoop QA commented on HADOOP-2451:
-----------------------------------
+1 overall. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12371841/patch.txt
against trunk revision r604999.
@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/1378/testReport/
Findbugs warnings:
http://lucene.zones.apache.org:8080/hudson/job/Hadoop-Patch/1378/artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html
Checkstyle results:
http://lucene.zones.apache.org:8080/hudson/job/Hadoop-Patch/1378/artifact/trunk/build/test/checkstyle-errors.html
Console output:
http://lucene.zones.apache.org:8080/hudson/job/Hadoop-Patch/1378/console
This message is automatically generated.
> [hbase] End key is incorrectly assigned in many region splits
> -------------------------------------------------------------
>
> Key: HADOOP-2451
> URL: https://issues.apache.org/jira/browse/HADOOP-2451
> 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
>
>
> When a region is split, the new child region for the upper half of the key
> range is always assigned as null (meaning end of table). If splits only
> happen at the end of the table, this is harmless. However under a random
> write load, an inner region is just as likely to split.
> This would explain why we have seen cases where after a split, there are
> multiple regions whose end key is the end of the table (null)
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
