accumulo-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "John Vines (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (ACCUMULO-3918) Different locality groups can compact with different iterator stacks
Date Thu, 25 Jun 2015 18:53:05 GMT

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

John Vines commented on ACCUMULO-3918:
--------------------------------------

I'm fine with it being an improvement. I feel it's a bit in an in between state.

I feel the same way about the various degrees of inconsistency. I feel reading the configuration
between each locality group causes too much inconsistency. I could settle with each compaction
using one config snapshot for the entire compaction. The conversation has just caused me to
think about if we're making compaction contracts weird for users by using fresh iterator stacks
for each locality group (which if we decide it is could be future work).

> Different locality groups can compact with different iterator stacks
> --------------------------------------------------------------------
>
>                 Key: ACCUMULO-3918
>                 URL: https://issues.apache.org/jira/browse/ACCUMULO-3918
>             Project: Accumulo
>          Issue Type: Improvement
>          Components: tserver
>    Affects Versions: 1.6.0
>            Reporter: John Vines
>
> While looking through the compactor code, I noticed that we load the iterator stack for
each locality group written and drop it when we're done. This means if a user reconfigures
iterators while a locality group is being written, the following locality groups will be compacted
inconsistently with the rest of the file.
> We should really read the stack once and be consistent for the entire file written.



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

Mime
View raw message