[
https://issues.apache.org/jira/browse/CASSANDRA-6146?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13931632#comment-13931632
]
Benedict commented on CASSANDRA-6146:
-------------------------------------
Hmm. Also, I didn't realise at all but all of those queries were failing
because the keyspace create didn't succeed. Which leads me to question how
we're reporting errors back. The litle number in the top-right was
incrementing, but I didn't realise this meant there were any errors as the
sample output listed all of the runs as a measurement. Also, once I opened the
error log it was completely empty (until I tried running again with it open, at
which point it starts filling up with errors)
This could lead to very wrong utilisation, and no one being any the wiser.
Ideally the regular output would discount errors from the samples, and report
them separately.
> CQL-native stress
> -----------------
>
> Key: CASSANDRA-6146
> URL: https://issues.apache.org/jira/browse/CASSANDRA-6146
> Project: Cassandra
> Issue Type: New Feature
> Components: Tools
> Reporter: Jonathan Ellis
> Fix For: 2.1 beta2
>
>
> The existing CQL "support" in stress is not worth discussing. We need to
> start over, and we might as well kill two birds with one stone and move to
> the native protocol while we're at it.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
