[
https://issues.apache.org/jira/browse/ACCUMULO-3918?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14601611#comment-14601611
]
Josh Elser commented on ACCUMULO-3918:
--------------------------------------
bq. And telling people to offline their tables is horrible advise. That's a
issue we should strengthen, not tell people to suffer through.
Well, it's the only consistent thing we have at the moment... It's not ideal,
but it does work. Can you ensure consistency for what you describe here given
the race-conditions for ZK-propagation in general? The problem as you described
it seems simple enough to fix, but I haven't looked to see if we'd just be
kicking the can down the road.
> 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)
