hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hadoop QA (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-10017) HRegionPartitioner, rows directed to last partition are wrongly mapped.
Date Thu, 21 Nov 2013 15:13:41 GMT

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

Hadoop QA commented on HBASE-10017:
-----------------------------------

{color:red}-1 overall{color}.  Here are the results of testing the latest attachment 
  http://issues.apache.org/jira/secure/attachment/12615133/HBASE-10017-v0.94.6.patch
  against trunk revision .

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

    {color:red}-1 tests included{color}.  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.

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

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

This message is automatically generated.

> HRegionPartitioner, rows directed to last partition are wrongly mapped.
> -----------------------------------------------------------------------
>
>                 Key: HBASE-10017
>                 URL: https://issues.apache.org/jira/browse/HBASE-10017
>             Project: HBase
>          Issue Type: Bug
>          Components: mapreduce
>    Affects Versions: 0.94.6
>            Reporter: Roman Nikitchenko
>             Fix For: 0.94.6
>
>         Attachments: HBASE-10017-v0.94.6.patch
>
>
> Inside HRegionPartitioner class there is getPartition() method which should map first
numPartitions regions to appropriate partitions 1:1. But based on condition last region is
hashed which could lead to last reducer not having any data. This is considered serious issue.
> I reproduced this only starting from 16 regions per table. Original defect was found
in 0.94.6 but at least today's trunk and 0.91 branch head have the same HRegionPartitioner
code in this part which means the same issue.



--
This message was sent by Atlassian JIRA
(v6.1#6144)

Mime
View raw message