[
https://issues.apache.org/jira/browse/CASSANDRA-8429?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14236997#comment-14236997
]
Ariel Weisberg commented on CASSANDRA-8429:
-------------------------------------------
Ok... bisecting off of trunk points to 9c316e7858f6dbf9df892aff78431044aa104ed9
I am ran the commit before e60a06cc866e5e85d3e58f25b98f8c048d07ad24 to make
sure it doesn't fail. It usually fails in two tries. I have done four and it
seems to work.
Two others have tried to reproduce the issue and not had any luck. I seem to be
doing something different to cause it. I am using CCM to start the one node
cluster with the attached cluster.conf. Server is on Ubuntu 14.04 on a
dedicated quad-core desktop with SSD, client is on a quad-core laptop, network
is gig-E.
> Stress on trunk fails mixed workload on missing keys
> ----------------------------------------------------
>
> Key: CASSANDRA-8429
> URL: https://issues.apache.org/jira/browse/CASSANDRA-8429
> Project: Cassandra
> Issue Type: Bug
> Environment: Ubuntu 14.04
> Reporter: Ariel Weisberg
> Assignee: Ariel Weisberg
>
> Starts as part of merge commit 25be46497a8df46f05ffa102bc645bfd684ea48a
> Stress will say that a key wasn't validated because it isn't returned even
> though it's loaded. The key will eventually appear and can be queried using
> cqlsh.
> Reproduce with
> #!/bin/sh
> rm /tmp/fark
> ROWCOUNT=10000000
> SCHEMA='-col n=fixed(1) -schema
> compaction(strategy=LeveledCompactionStrategy) compression=LZ4Compressor'
> ./cassandra-stress write n=$ROWCOUNT -node xh61 -pop seq=1..$ROWCOUNT no-wrap
> -rate threads=25 $SCHEMA
> ./cassandra-stress mixed "ratio(read=2)" n=100000000 -node xh61 -pop
> "dist=extreme(1..$ROWCOUNT,0.6)" -rate threads=25 $SCHEMA
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
