You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Jaydeepkumar Chovatia (JIRA)" <ji...@apache.org> on 2017/11/30 00:27:00 UTC
[jira] [Commented] (CASSANDRA-14078) Fix dTest
test_bulk_round_trip_blogposts_with_max_connections
[ https://issues.apache.org/jira/browse/CASSANDRA-14078?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16271882#comment-16271882 ]
Jaydeepkumar Chovatia commented on CASSANDRA-14078:
---------------------------------------------------
|| branch || build ||
| [master|https://github.com/apache/cassandra-dtest/compare/master...jaydeepkumar1984:CASSANDRA-14078?expand=1] | [circleci | https://circleci.com/gh/jaydeepkumar1984/cassandra-dtest/4] |
> Fix dTest test_bulk_round_trip_blogposts_with_max_connections
> -------------------------------------------------------------
>
> Key: CASSANDRA-14078
> URL: https://issues.apache.org/jira/browse/CASSANDRA-14078
> Project: Cassandra
> Issue Type: Test
> Components: Testing
> Reporter: Jaydeepkumar Chovatia
> Assignee: Jaydeepkumar Chovatia
> Priority: Minor
>
> This ticket is regarding following dTest {{cqlsh_tests.cqlsh_copy_tests.CqlshCopyTest.test_bulk_round_trip_blogposts_with_max_connections}}
> This test is trying to limit number of client connections and assumes that once connection count has reached then client will fail-over to other node and do the request. The reason is, it is not deterministic test case as it totally depends on what hardware you run, timing, etc.
> For example
> If we look at https://builds.apache.org/view/A-D/view/Cassandra/job/Cassandra-trunk-dtest/353/testReport/cqlsh_tests.cqlsh_copy_tests/CqlshCopyTest/test_bulk_round_trip_blogposts_with_max_connections/
> {{
> ...
> Processed: 5000 rows; Rate: 2551 rows/s; Avg. rate: 2551 rows/s
> All replicas busy, sleeping for 4 second(s)...
> Processed: 10000 rows; Rate: 2328 rows/s; Avg. rate: 2307 rows/s
> All replicas busy, sleeping for 1 second(s)...
> Processed: 15000 rows; Rate: 2137 rows/s; Avg. rate: 2173 rows/s
> All replicas busy, sleeping for 11 second(s)...
> Processed: 20000 rows; Rate: 2138 rows/s; Avg. rate: 2164 rows/s
> Processed: 25000 rows; Rate: 2403 rows/s; Avg. rate: 2249 rows/s
> Processed: 30000 rows; Rate: 2582 rows/s; Avg. rate: 2321 rows/s
> Processed: 35000 rows; Rate: 2835 rows/s; Avg. rate: 2406 rows/s
> Processed: 40000 rows; Rate: 2867 rows/s; Avg. rate: 2458 rows/s
> Processed: 45000 rows; Rate: 3163 rows/s; Avg. rate: 2540 rows/s
> Processed: 50000 rows; Rate: 3200 rows/s; Avg. rate: 2596 rows/s
> Processed: 50234 rows; Rate: 2032 rows/s; Avg. rate: 2572 rows/s
> All replicas busy, sleeping for 23 second(s)...
> Replicas too busy, given up
> ...
> }}
> Here we can see request is timing out, sometimes it resumes after 1 second, next time 11 seconds and some times it doesn't work at all.
> In my opinion this test is not a good fit for dTest as dTest(s) should be deterministic.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@cassandra.apache.org
For additional commands, e-mail: commits-help@cassandra.apache.org