cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ariel Weisberg (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-9741) cfhistograms dtest flaps on trunk and 2.2
Date Tue, 28 Jul 2015 14:45:06 GMT

    [ https://issues.apache.org/jira/browse/CASSANDRA-9741?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14644467#comment-14644467
] 

Ariel Weisberg commented on CASSANDRA-9741:
-------------------------------------------

This kind of looks like overload to me. It's loading 15 million rows RF=3 200 threads with
no rate limit. I don't know if this always worked and things got slower. I think the place
to address that is by adding performance graphs and workloads and building a backlog of tested
revisions.

I changed to 25 threads and it works. Will try 50 next.

I would like to fold this test into the CVH harness. It takes forever to run doesn't look
like good bang for the buck compute time wise. I want to keep an eye out for low hanging fruit
we can remove from dtests into the CVH to reduce the cost of what we run on each commit.

> cfhistograms dtest flaps on trunk and 2.2
> -----------------------------------------
>
>                 Key: CASSANDRA-9741
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-9741
>             Project: Cassandra
>          Issue Type: Bug
>            Reporter: Jim Witschey
>            Assignee: Ariel Weisberg
>             Fix For: 2.2.x, 3.0.x
>
>
> {{jmx_test.py:TestJMX.cfhistograms_test}} flaps on CassCI under trunk and 2.2.
> On 2.2, it fails one of its assertions when {{'Unable to compute when histogram overflowed'}}
is found in the output of {{nodetool cfhistograms}}. Here's the failure history for 2.2:
> http://cassci.datastax.com/view/cassandra-2.2/job/cassandra-2.2_dtest/lastCompletedBuild/testReport/junit/jmx_test/TestJMX/cfhistograms_test/history/
> On trunk, it fails when an error about a {{WriteFailureException}} during hinted handoff
is found in the C* logs after the tests run ([example cassci output|http://cassci.datastax.com/view/trunk/job/trunk_dtest/315/testReport/junit/jmx_test/TestJMX/cfhistograms_test/]).
Here's the failure history for trunk:
> http://cassci.datastax.com/view/trunk/job/trunk_dtest/lastCompletedBuild/testReport/junit/jmx_test/TestJMX/cfhistograms_test/history/
> I haven't seen it fail locally yet, but haven't run the test more than a couple times
because it takes a while.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message