You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Jean-Daniel Cryans (JIRA)" <ji...@apache.org> on 2013/08/22 22:47:52 UTC

[jira] [Updated] (HBASE-9307) HalfStoreFileReader needs to handle the faked key else compactions go into infinite loops

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

Jean-Daniel Cryans updated HBASE-9307:
--------------------------------------

    Status: Patch Available  (was: Open)
    
> HalfStoreFileReader needs to handle the faked key else compactions go into infinite loops
> -----------------------------------------------------------------------------------------
>
>                 Key: HBASE-9307
>                 URL: https://issues.apache.org/jira/browse/HBASE-9307
>             Project: HBase
>          Issue Type: Bug
>    Affects Versions: 0.95.2
>            Reporter: Jean-Daniel Cryans
>            Assignee: Jean-Daniel Cryans
>            Priority: Critical
>             Fix For: 0.98.0, 0.95.3
>
>         Attachments: HBASE-9307.patch
>
>
> I found this while trying out 0.95.2
> I couldn't shut my cluster down because one region was still compacting, but it already had been doing that for an hour and it only had 80MBs of data.
> Debugging I saw that it was a post-split compaction, specifically for the top part of the HFiles, and that it was just spinning on the first entry in the file.
> Eventually I saw that the anonymous HFileScanner inside HalfStoreFileReader.getScanner (that's so dirty) wasn't handling HConstants.INDEX_KEY_MAGIC in seekTo() when calling this:
> bq. this.delegate.seekTo(splitkey)
> Instead it would treat this as if the split key wasn't in the file, but still seek back to the beginning of the file *then read on from there*.
> During the compaction it would see a KV that's not even part of the region, and it just tries to find the correct block over and over again.
> This came from HBASE-7845.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira