[
https://issues.apache.org/jira/browse/CASSANDRA-7695?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aleksey Yeschenko updated CASSANDRA-7695:
-----------------------------------------
Priority: Blocker (was: Critical)
Assignee: T Jake Luciani (was: Aleksey Yeschenko)
CASSANDRA-6861 introduced it (bc4b008bf138f3542f228624b9e9a4a4301ea8b2). The
commit before it (9030693180b1e6484ae7d1d44ef6964ca9491f49) is clean.
Reassigning back to [~tjake]
To repro, can use https://github.com/iamaleksey/castorture/tree/7695
> 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: T Jake Luciani
> Priority: Blocker
> 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)
