[
https://issues.apache.org/jira/browse/CASSANDRA-8608?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14280458#comment-14280458
]
T Jake Luciani commented on CASSANDRA-8608:
-------------------------------------------
{code}
diff --git a/conf/cassandra.yaml b/conf/cassandra.yaml
index 24bab09..0dbc6b0 100644
--- a/conf/cassandra.yaml
+++ b/conf/cassandra.yaml
@@ -547,7 +547,7 @@ column_index_size_in_kb: 64
batch_size_warn_threshold_in_kb: 5
# Fail any batch exceeding this value. 50kb (10x warn threshold) by default.
-batch_size_fail_threshold_in_kb: 50
+batch_size_fail_threshold_in_kb: 500
{code}
The stress cmd line is:
{code}
./tools/bin/cassandra-stress user profile=partition.yaml ops\(insert=1\)
n=10000000000 -rate threads=50
{code}
> Fix cassandra-stress bug introduced by 7964, and cleanup related code a little
> ------------------------------------------------------------------------------
>
> Key: CASSANDRA-8608
> URL: https://issues.apache.org/jira/browse/CASSANDRA-8608
> Project: Cassandra
> Issue Type: Bug
> Reporter: Benedict
> Assignee: Benedict
>
> 7964 had a very basic mistake present when wiring up writes - the "limit" was
> not reset, so only the first row would be returned (the fact _ANY_ row was
> returned was itself sort-of a bug in this scenario, and I've changed this
> also). At the same time I've changed the definition of limit to lastRow so
> that the related functionality is clearer and more obviously correct.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
