hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andrew Purtell (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (HBASE-3325) Optimize log splitter to not output obsolete edits
Date Sat, 19 Jul 2014 00:43:38 GMT

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

Andrew Purtell resolved HBASE-3325.

    Resolution: Not a Problem
      Assignee:     (was: Aravind Menon)

Didn't happen

> Optimize log splitter to not output obsolete edits
> --------------------------------------------------
>                 Key: HBASE-3325
>                 URL: https://issues.apache.org/jira/browse/HBASE-3325
>             Project: HBase
>          Issue Type: Improvement
>          Components: master, regionserver
>    Affects Versions: 0.92.0
>            Reporter: Todd Lipcon
> Currently when the master splits logs, it outputs all edits it finds, even those that
have already been obsoleted by flushes. At replay time on the RS we discard the edits that
have already been flushed.
> We could do a pretty simple optimization here - basically the RS should replicate a map
"region id -> last flushed seq id" into ZooKeeper (this can be asynchronous by some seconds
without any problems). Then when doing log splitting, if we have this map available, we can
discard any edits found in the logs that were already flushed, and thus output a much smaller
amount of data.

This message was sent by Atlassian JIRA

View raw message