hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Todd Lipcon (Commented) (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-5311) Allow inmemory Memstore compactions
Date Wed, 08 Feb 2012 08:26:01 GMT

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

Todd Lipcon commented on HBASE-5311:
------------------------------------

The assumption with the code I was writing was a single "flusher" thread -- which could be
enforced by making the "flush/compact" stuff synchronized on a separate lock. The idea is
basically to allow the common case to run lockless and push all the effort to whoever wants
to make updates to the data structure.
                
> Allow inmemory Memstore compactions
> -----------------------------------
>
>                 Key: HBASE-5311
>                 URL: https://issues.apache.org/jira/browse/HBASE-5311
>             Project: HBase
>          Issue Type: Improvement
>            Reporter: Lars Hofhansl
>         Attachments: InternallyLayeredMap.java
>
>
> Just like we periodically compact the StoreFiles we should also periodically compact
the MemStore.
> During these compactions we eliminate deleted cells, expired cells, cells to removed
because of version count, etc, before we even do a memstore flush.
> Besides the optimization that we could get from this, it should also allow us to remove
the special handling of ICV, Increment, and Append (all of which use upsert logic to avoid
accumulating excessive cells in the Memstore).
> Not targeting this.

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