You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Alex Newman (JIRA)" <ji...@apache.org> on 2014/08/14 01:10:12 UTC
[jira] [Commented] (HBASE-10017) HRegionPartitioner, rows directed
to last partition are wrongly mapped.
[ https://issues.apache.org/jira/browse/HBASE-10017?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14096275#comment-14096275 ]
Alex Newman commented on HBASE-10017:
-------------------------------------
I assume this has been fixed?
> 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
> Priority: Critical
> Attachments: HBASE-10017-r1544633.patch, HBASE-10017-r1544633.patch, TEST-org.apache.hadoop.hbase.mapreduce.IntegrationTestBulkLoad.xml.gz, TestHRegionServerBulkLoad-more-splits.txt, TestHRegionServerBulkLoad-more-splits.txt, patchSiteOutput.txt
>
>
> 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.2#6252)