accumulo-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Christopher Tubbs (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (ACCUMULO-3603) replay mutations to the wrong table?
Date Thu, 12 Mar 2015 19:15:40 GMT

     [ https://issues.apache.org/jira/browse/ACCUMULO-3603?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Christopher Tubbs updated ACCUMULO-3603:
----------------------------------------
    Fix Version/s:     (was: 1.6.3)

> 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
>          Time Spent: 1.5h
>  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)

Mime
View raw message