hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hudson (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-15126) HBaseFsck's checkRegionBoundaries function sets incorrect 'storesFirstKey'
Date Thu, 21 Jan 2016 19:52:39 GMT

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

Hudson commented on HBASE-15126:
--------------------------------

FAILURE: Integrated in HBase-Trunk_matrix #649 (See [https://builds.apache.org/job/HBase-Trunk_matrix/649/])
HBASE-15126 HBaseFsck's checkRegionBoundaries function sets incorrect (tedyu: rev 1d2b0d831117e033aebf0b347b162c4483a04e5d)
* hbase-server/src/main/java/org/apache/hadoop/hbase/util/HBaseFsck.java
* hbase-server/src/test/java/org/apache/hadoop/hbase/util/TestHBaseFsckOneRS.java


> HBaseFsck's checkRegionBoundaries function sets incorrect 'storesFirstKey'
> --------------------------------------------------------------------------
>
>                 Key: HBASE-15126
>                 URL: https://issues.apache.org/jira/browse/HBASE-15126
>             Project: HBase
>          Issue Type: Bug
>          Components: hbck
>    Affects Versions: 2.0.0
>            Reporter: chenrongwei
>            Assignee: chenrongwei
>             Fix For: 2.0.0
>
>         Attachments: HBASE-15126-v001.patch, HBASE-15126-v002.patch, HBASE-15126-v003.patch,
HBASE-15126-v004.patch, HBASE-15126-v005.patch, HBASE-15126-v006.patch
>
>
> HBaseFsck's checkRegionBoundaries function set the 'currentRegionBoundariesInformation.storesFirstKey'
 was incorrect.I think it should be set like below,
> currentRegionBoundariesInformation.storesFirstKey = keyOnly(storeFirstKey);
> but current the 'currentRegionBoundariesInformation.storesFirstKey ' is just set to 'storeFirstKey',which
will cause to comparator.compare(currentRegionBoundariesInformation.storesFirstKey,
>             currentRegionBoundariesInformation.metaFirstKey)  get a wrong result.  Because
it just compared the rowkey's length.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message