hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Roman Nikitchenko (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (HBASE-10017) HRegionPartitioner, rows directed to last partition are wrongly mapped.
Date Fri, 22 Nov 2013 18:49:35 GMT

     [ https://issues.apache.org/jira/browse/HBASE-10017?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Roman Nikitchenko updated HBASE-10017:
--------------------------------------

    Attachment: HBASE-10017-r1544633.patch

Actually there is 3 sub-issues fixes which lead to final issue and UT update.
[!] Fixed HRegionPartitioner getLog() class name.
[!] Fixed mapping of regions to last partitioner.
[!] Fixed equal distribution for region -> partitioner mapping starting from 30.
[+] Improved TestHRegionPartitioner. Checked it really fails without change. 


> 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
>         Attachments: HBASE-10017-r1544633.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