[
https://issues.apache.org/jira/browse/ACCUMULO-3918?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14601656#comment-14601656
]
Christopher Tubbs commented on ACCUMULO-3918:
---------------------------------------------
bq. We know that ZK has a defined window for propagation,
Is that true? We know ZK has a defined window to maintain its session, but I
don't think we have a defined window for any particular set of observers on a
ZK watcher to complete and the ZooCache/TableConfiguration to be updated.
> 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)
