[
https://issues.apache.org/jira/browse/CASSANDRA-7695?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aleksey Yeschenko updated CASSANDRA-7695:
-----------------------------------------
Since Version: 2.1 rc1 (was: 2.1 rc4)
The bug is legit. Closing in on the cause right now.
FWIW, beta2 is unaffected, so it was introduced in rc1. Also, the issue only
manifests when large values are being concurrently overwritten - ~100KB and
larger.
Will update w/ new details shortly.
> Inserting the same row in parallel causes bad data to be returned to the
> client
> -------------------------------------------------------------------------------
>
> Key: CASSANDRA-7695
> URL: https://issues.apache.org/jira/browse/CASSANDRA-7695
> Project: Cassandra
> Issue Type: Bug
> Environment: Linux 3.12.21, JVM 1.7u60
> Cassandra server 2.1.0 RC 5
> Cassandra datastax client version 2.1.0RC1
> Reporter: Johan Bjork
> Assignee: Aleksey Yeschenko
> Priority: Critical
> Fix For: 2.1.0
>
> Attachments: PutFailureRepro.java, bad-data-tid43-get,
> bad-data-tid43-put
>
>
> Running the attached test program against a cassandra 2.1 server results in
> scrambled data returned by the SELECT statement. Running it against latest
> stable works fine.
> Attached:
> * Program that reproduces the failure
> * Example output files from mentioned test-program with the scrambled output.
> Failure mode:
> The value returned by 'get' is scrambled, the size is correct but some bytes
> have shifted locations in the returned buffer.
> Cluster info:
> For the test we set up a single cassandra node using the stock configuration
> file.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
