[
https://issues.apache.org/jira/browse/ACCUMULO-3603?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14327968#comment-14327968
]
Eric Newton edited comment on ACCUMULO-3603 at 2/19/15 7:15 PM:
----------------------------------------------------------------
I created an integration test that batch writes into multiple tables, and
verifies that mutations went into the correct tables. Everything worked as
expected.
was (Author: ecn):
I created a unit test that batch writes into multiple tables, and verifies that
mutations went into the correct tables. Everything worked as expected.
> replay mutations to the wrong table?
> ------------------------------------
>
> Key: ACCUMULO-3603
> URL: https://issues.apache.org/jira/browse/ACCUMULO-3603
> Project: Accumulo
> Issue Type: Bug
> Components: tserver
> Affects Versions: 1.6.1
> Reporter: Eric Newton
> Assignee: Eric Newton
> Priority: Critical
> Fix For: 1.6.3
>
> Time Spent: 1h 20m
> Remaining Estimate: 0h
>
> A user writes to the mailing list:
> {quote}
> Few times I noticed that some tables have values they cannot have, and
> those entries have timestamp close to a tabletserver failure time.
> (I mean wrong format, one table has msgpack values at least 10 bytes
> long and another table has 1-byte values and after a failure I read
> one or two 1-byte values in the table where I expect to read msgpack).
> I suspect that during recovery process, when WAL is being read, some
> entries are inserted to a wrong table.
> May be it is a know bug as I am still using Accumulo 1.6.1
> {quote}
> Consider adding multiple tables to the continuous ingest test to reproduce.
> Note that the random walk test certainly does this, and no failures have been
> observed.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
