You are viewing a plain text version of this content. The canonical link for it is here.

Posted to notifications@accumulo.apache.org by "John Vines (JIRA)" <ji...@apache.org> on 2013/04/17 00:09:16 UTC

[jira] [Commented] (ACCUMULO-1281) flush the METADATA table after GC

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

John Vines commented on ACCUMULO-1281:
--------------------------------------

Do we want to do it after every run or every Nth?

Or perhaps this makes for the case that the !METADATA table should have a smaller in memory map, but that sounds like a bad idea.
                
> flush the METADATA table after GC
> ---------------------------------
>
>                 Key: ACCUMULO-1281
>                 URL: https://issues.apache.org/jira/browse/ACCUMULO-1281
>             Project: Accumulo
>          Issue Type: Improvement
>          Components: gc
>            Reporter: Eric Newton
>            Assignee: Eric Newton
>            Priority: Trivial
>             Fix For: 1.5.0
>
>
> The METADATA table is often small, with many in-memory writes.  Because it is small, it does not normally get flushed, which will prune data with the versioning/delete iterators.  Over time, the many in-memory versions can cause poor performance.
> The file garbage collector (gc) will make lots of updates as it runs.  That would be a perfect time to flush the table and prune the versions.

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