Mailing-List: contact notifications-help@accumulo.apache.org; run by ezmlm
Precedence: bulk
Reply-To: jira@apache.org
Date: Wed, 17 Dec 2014 19:01:14 +0000 (UTC)
From: "Christopher Tubbs (JIRA)" <jira@apache.org>
To: notifications@accumulo.apache.org
Message-ID: <JIRA.12529298.1319829092000.47608.1418842874128@Atlassian.JIRA>
In-Reply-To: <JIRA.12529298.1319829092000@Atlassian.JIRA>
References: <JIRA.12529298.1319829092000@Atlassian.JIRA>
 <JIRA.12529298.1319829092682@arcas>
Subject: [jira] [Commented] (ACCUMULO-96) Need to handle case where tablet
 has lots of delete entries
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

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

I think the case still has merit. I don't know if anybody's interested in working on it.

> 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
>
> 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.4#6332)