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

["Christopher Tubbs (JIRA)" <ji...@apache.org>]

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

Christopher Tubbs commented on ACCUMULO-96:
-------------------------------------------

[~kturner], you marked this issue as resolved, with your change in ACCUMULO-4501. Can you add more explanation here how that commit addresses this issue? I assume you've added the ability to keep track of the number of deletes for a tablet, but did you do anything else to facilitate this issue?

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