You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@accumulo.apache.org by "Christopher Tubbs (JIRA)" <ji...@apache.org> on 2015/10/23 00:07:27 UTC
[jira] [Assigned] (ACCUMULO-3235) No-chop merges
[ https://issues.apache.org/jira/browse/ACCUMULO-3235?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Christopher Tubbs reassigned ACCUMULO-3235:
-------------------------------------------
Assignee: Christopher Tubbs
> No-chop merges
> --------------
>
> Key: ACCUMULO-3235
> URL: https://issues.apache.org/jira/browse/ACCUMULO-3235
> Project: Accumulo
> Issue Type: Improvement
> Components: tserver
> Reporter: Christopher Tubbs
> Assignee: Christopher Tubbs
> Fix For: 1.8.0
>
>
> Merges currently require a special "chop" major compaction, which can be slow. The idea is simple: in the metadata entries for files, we track the range in use for that file with a notation.
> This additional metadata would be used to merge tablets without re-writing data. Only this extra metadata would be updated (to a narrower range when split, and possibly collapsed if merging adjacent ranges). If a range is missing for a file, the tablet's range will be used instead. This simplifies things for backwards compatibility, and means we don't need to include a redundant range if the tablet isn't splitting/merging.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)