You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@accumulo.apache.org by "Keith Turner (JIRA)" <ji...@apache.org> on 2017/03/20 15:07:42 UTC

[jira] [Updated] (ACCUMULO-96) Need to handle case where tablet has lots of delete entries

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

Keith Turner updated ACCUMULO-96:
---------------------------------
    Fix Version/s: 2.0.0

> Need to handle case where tablet has lots of delete entries
> -----------------------------------------------------------
>
>                 Key: ACCUMULO-96
>                 URL: https://issues.apache.org/jira/browse/ACCUMULO-96
>             Project: Accumulo
>          Issue Type: Bug
>          Components: tserver
>            Reporter: Keith Turner
>            Assignee: Keith Turner
>             Fix For: 2.0.0
>
>          Time Spent: 10m
>  Remaining Estimate: 0h
>
> Currently Accumulo only drops delete entries when its major compacting all files.  All files may never be compacted.  Lots of delete entries building up can be problematic for scan performance.
> Possible solutions :
>  * Keep a count of the # of delete entries per file.  Compact all when the ratio of delete entries to entries crosses a threshold.
>  * When a scan encounters a tablet w/ a lot of delete entries, schedule a majc.  This is reactive, but removes the need for bookkeeping in the previous solution. 



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)