[
https://issues.apache.org/jira/browse/CASSANDRA-6146?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13932576#comment-13932576
]
Benedict commented on CASSANDRA-6146:
-------------------------------------
bq. That is "Error/fatal counter". You've seen the empty log because you've
opened the "Log Viewer" after those errors had happened. But all your errors
were logged into jmeter.log as well (which should be in your ~ dir), so you can
inspect them there. But beware, Jmeter overwrites that log every time it is
started.
Right, I understand this. What I'm suggesting is that it is by chance that I
understand this, and that a user with an improperly configured cluster may get
completely bogus answers without realising this, so I hope we can do something
to make it more obvious without digging through Jmeter docs, which let's face
it, nobody is going to do :-)
> 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)
