accumulo-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Christopher Tubbs (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (ACCUMULO-3885) Shouldn't short circuit multiple compaction requests if iterators have changed
Date Thu, 04 Jun 2015 18:01:39 GMT

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

Christopher Tubbs updated ACCUMULO-3885:
----------------------------------------
    Fix Version/s: 1.8.0

> Shouldn't short circuit multiple compaction requests if iterators have changed
> ------------------------------------------------------------------------------
>
>                 Key: ACCUMULO-3885
>                 URL: https://issues.apache.org/jira/browse/ACCUMULO-3885
>             Project: Accumulo
>          Issue Type: Bug
>          Components: tserver
>    Affects Versions: 1.6.0
>            Reporter: John Vines
>             Fix For: 1.8.0
>
>
> Currently if you force a compaction and then force another one, accumulo has a convenience
feature that doesn't force the redundant one. The problem is if you change iterators settings
for majc time between compaction calls, the second one is no longer redundant and the feature
is now a hindrance. We should compare state of the iterators between the currently running
compaction and the current state before decided to drop the second attempt.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message