[
https://issues.apache.org/jira/browse/ACCUMULO-3918?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
John Vines updated ACCUMULO-3918:
---------------------------------
Comment: was deleted
(was: As I mentioned with Josh, tracking by locality group doesn't scale it as
well because you could have a lot of locality groups. I am currently
questioning the gain of building fresh iterator stacks for each locality group,
especially do we don't have any behavior like this during scan time. We should
be consistent about how the iterators are created and access data because it
could add a lot of weird cases for user iterators.)
> 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)
