hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Nicolas Spiegelberg (Updated) (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (HBASE-4645) Edits Log recovery losing data across column families
Date Fri, 28 Oct 2011 03:33:32 GMT

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

Nicolas Spiegelberg updated HBASE-4645:
---------------------------------------

       Resolution: Fixed
    Fix Version/s: 0.94.0
                   0.92.0
           Status: Resolved  (was: Patch Available)
    
> Edits Log recovery losing data across column families
> -----------------------------------------------------
>
>                 Key: HBASE-4645
>                 URL: https://issues.apache.org/jira/browse/HBASE-4645
>             Project: HBase
>          Issue Type: Bug
>    Affects Versions: 0.89.20100924, 0.92.0
>            Reporter: Amitanand Aiyer
>            Assignee: Amitanand Aiyer
>             Fix For: 0.92.0, 0.94.0
>
>         Attachments: 4645-v9.diff
>
>
> There is a data loss happening (for some of the column families) when we do the replay
logs.
> The bug seems to be from the fact that during replay-logs we only choose to replay
> the logs from the maximumSequenceID across *ALL* the stores. This is wrong. If a
> column family is ahead of others (because the crash happened before all the column
> families were flushed), then we lose data for the column families that have not yet
> caught up.
> The correct logic for replay should begin the replay from the minimum across the
> maximum in each store. 

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message