Benedict commented on CASSANDRA-7695:


Would prefer we call the test NativeTransportBufferRecycleTest, and comment it 
to explain. Also remove the LOCAL_QUORUM, since it's meaningless here and don't 
want to confuse future readers. It's also not clear why we're bothering to 
'dump keys', but this is a test so I'm not going to vet it too hard.

> 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: 7695-workaround.txt, 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

Reply via email to