accumulo-notifications mailing list archives

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


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:
>             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

View raw message