[
https://issues.apache.org/jira/browse/ACCUMULO-3918?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14601361#comment-14601361
]
John Vines commented on ACCUMULO-3918:
--------------------------------------
Auditing. Being able to debug an iterator stack that has experienced
strangeness requires knowing what iterator settings were used when. If they're
constantly being rebuilt mid-file, I know must track all information changes by
locality group and not by file. And if I have a very heavy iterator stack which
uses deep copies in major compactions to reference information outside the
locality group, I could end up with data on disk which is inconsistent with how
it was written.
> 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: Bug
> 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)
