hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sergey Shelukhin (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-6508) [0.89-fb] Filter out edits at log split time
Date Mon, 22 Oct 2012 20:24:12 GMT

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

Sergey Shelukhin commented on HBASE-6508:
-----------------------------------------

It appears that new message will not be processed correctly by the old server on new protocols.

Looks like we won't be porting this...
                
> [0.89-fb] Filter out edits at log split time
> --------------------------------------------
>
>                 Key: HBASE-6508
>                 URL: https://issues.apache.org/jira/browse/HBASE-6508
>             Project: HBase
>          Issue Type: Improvement
>          Components: master, regionserver, wal
>    Affects Versions: 0.89-fb
>            Reporter: Alex Feinberg
>            Assignee: Alex Feinberg
>             Fix For: 0.89-fb
>
>
> At log splitting time, we can filter out many edits if we have a conservative estimate
of what was saved last in each region.
> This patch does the following:
> 1) When a region server flushes a MemStore to HFile, store the last flushed sequence
id for the region in a map.
> 2) Send the map to master it as a part of the region server report.
> 3) Adds an RPC call in HMasterRegionInterface to allow a region server to query the last
last flushed sequence id for a region.
> 4) Skips any log entry with sequence id lower than last flushed sequence id for the region
during log split time.
> 5) When a region is removed from a region server, removed the the entry for that region
from the map, so that it isn't sent during the next report.
> This can reduce downtime when a regionserver goes down quite a bit.

--
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

Mime
View raw message