accumulo-notifications mailing list archives

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


Christopher Tubbs commented on ACCUMULO-3918:

Users don't have insight into where locality groups are stored (same file or otherwise), and
we don't make any API-contract type guarantees to the user regarding how locality groups are
"physically" stored, so how would user experience benefit from knowing that a consistent iterator
stack was used for all locality groups in a file? And, what makes the scope of "file" better
than the scope of "locality group" (in other applications, these may even be the same thing)?

> 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