[
https://issues.apache.org/jira/browse/CASSANDRA-6074?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13773850#comment-13773850
]
Ryan McGuire commented on CASSANDRA-6074:
-----------------------------------------
0fc15e was actually chosen by 'git bisect'.
[code]
git bisect start
# good: [03045ca22b11b0e5fc85c4fabd83ce6121b5709b] Update versions for 2.0
final release
git bisect good 03045ca22b11b0e5fc85c4fabd83ce6121b5709b
# bad: [eb96db6c19515e6d1215230f29d25b46fcd005ef] Update versions for 2.0.1
release
git bisect bad eb96db6c19515e6d1215230f29d25b46fcd005ef
# bad: [31f6ec1bf5ac642ea0e47e40e62add46901135fc] Improve error message when
yaml contains invalid properties patch by Mikhail Stepura; reviewed by jbellis
for CASSANDRA-5958
git bisect bad 31f6ec1bf5ac642ea0e47e40e62add46901135fc
# bad: [6213cc89c94c9df1c480f541a194da0fe0edb6f6] Merge branch
'cassandra-2.0.0' into cassandra-2.0
git bisect bad 6213cc89c94c9df1c480f541a194da0fe0edb6f6
# bad: [0fc15e5ebd211a0921aee805b4f883ae6e2f728d] Merge branch
'cassandra-2.0.0' into cassandra-2.0
git bisect bad 0fc15e5ebd211a0921aee805b4f883ae6e2f728d
# good: [bb3f09c4b189d27bf136ad9df044d378019607d5] Merge branch
'cassandra-2.0.0' into cassandra-2.0
git bisect good bb3f09c4b189d27bf136ad9df044d378019607d5
# good: [cfadbb8b5fc9d7891cf57ae1ebe37936a4e7c24f] Merge branch
'cassandra-2.0.0' into cassandra-2.0
git bisect good cfadbb8b5fc9d7891cf57ae1ebe37936a4e7c24f
# good: [9806b7761fa035665959bc3a7434d535021c7d7d] Merge branch
'cassandra-2.0.0' into cassandra-2.0
git bisect good 9806b7761fa035665959bc3a7434d535021c7d7d
# good: [9a154a9ab949da5860b7d1d633792bb4edccdf73] Merge branch
'cassandra-2.0.0' into cassandra-2.0
git bisect good 9a154a9ab949da5860b7d1d633792bb4edccdf73
# good: [58d8dd40c377088c7f45eeaacefbfe5641c88d81] Merge branch
'cassandra-2.0.0' into cassandra-2.0
git bisect good 58d8dd40c377088c7f45eeaacefbfe5641c88d81
[code]
However, I just [redid this test this
morning|http://ryanmcguire.info/ds/graph/graph.html?stats=stats.6074.58d8dd_vs_0fc15e5.json&metric=interval_op_rate&operation=stress-read&smoothing=4]
... and it appears that it's fine :|
> Read regression in 2.0.1
> ------------------------
>
> Key: CASSANDRA-6074
> URL: https://issues.apache.org/jira/browse/CASSANDRA-6074
> Project: Cassandra
> Issue Type: Bug
> Reporter: Ryan McGuire
> Attachments: 6074 bisect.png, stress 2.0.0 vs 2.0.01.png
>
>
> I'm seeing a regression in stress reads introduced in 2.0.1. Note, that this
> is a separate regression from CASSANDRA-5933.
> Setup
> * 4 node cluster using default settings
> * Write: -F 30000000 -n 30000000 -i 5 -l 2
> * Read: -n 30000000 -o read -i 5
> I tried this three times on 2.0.0 and on 2.0.1(tentative; eb96db6c)
> 2.0.0 is fine, but 2.0.1 timed out of it's read 2 out of the 3 times, and on
> the one that did succeed, it struggled quite a bit at the start:
> !stress 2.0.0 vs 2.0.01.png!
> [Data can be viewed
> here|http://ryanmcguire.info/ds/graph/graph.html?stats=stats.2.0.0v2.0.1.json&metric=interval_op_rate&operation=stress-read&smoothing=4]
> I will bisect and update this when I find the commit that introduced this.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
