cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Russ Hatch (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-12249) dtest failure in upgrade_tests.paging_test.TestPagingDataNodes3RF3_Upgrade_current_3_0_x_To_indev_3_x.basic_paging_test
Date Tue, 09 Aug 2016 22:52:20 GMT

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

Russ Hatch commented on CASSANDRA-12249:
----------------------------------------

No problem -- job is here: http://cassci.datastax.com/view/Dev/view/knifewine/job/knifewine-upgrade_thobbs_12249-3.8-upgrade/

The job should queue up soon as build #1. Should take maybe 4-6 hours once started (will run
on ec2 w/10 nodes to match the last run of the 3.8 upgrade job).

If you're using the autojobs setup, feel free to push branches with 'upgrade' somewhere in
the name, and the autojobs system will build an upgrade job for you which you can run on-demand.
If you do that, I'd suggest ec2 for now since openstack has been a bit more noisy thus far
wrt upgrades.

> dtest failure in upgrade_tests.paging_test.TestPagingDataNodes3RF3_Upgrade_current_3_0_x_To_indev_3_x.basic_paging_test
> -----------------------------------------------------------------------------------------------------------------------
>
>                 Key: CASSANDRA-12249
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-12249
>             Project: Cassandra
>          Issue Type: Bug
>            Reporter: Philip Thompson
>            Assignee: Tyler Hobbs
>              Labels: dtest
>             Fix For: 3.8
>
>         Attachments: node1.log, node1_debug.log, node1_gc.log, node2.log, node2_debug.log,
node2_gc.log
>
>
> example failure:
> http://cassci.datastax.com/job/cassandra-3.8_dtest_upgrade/1/testReport/upgrade_tests.paging_test/TestPagingDataNodes3RF3_Upgrade_current_3_0_x_To_indev_3_x/basic_paging_test
> Failed on CassCI build cassandra-3.8_dtest_upgrade #1
> This is on a mixed version cluster, one node is 3.0.8 and the other is 3.8-tentative.
> Stack trace looks like:
> {code}
> ERROR [MessagingService-Incoming-/127.0.0.1] 2016-07-20 04:51:02,836 CassandraDaemon.java:201
- Exception in thread Thread[MessagingService-Incoming-/127.0.0.1,5,main]
> java.lang.AssertionError: null
> 	at org.apache.cassandra.db.ReadCommand$LegacyPagedRangeCommandSerializer.deserialize(ReadCommand.java:1042)
~[apache-cassandra-3.0.8.jar:3.0.8]
> 	at org.apache.cassandra.db.ReadCommand$LegacyPagedRangeCommandSerializer.deserialize(ReadCommand.java:964)
~[apache-cassandra-3.0.8.jar:3.0.8]
> 	at org.apache.cassandra.net.MessageIn.read(MessageIn.java:98) ~[apache-cassandra-3.0.8.jar:3.0.8]
> 	at org.apache.cassandra.net.IncomingTcpConnection.receiveMessage(IncomingTcpConnection.java:201)
~[apache-cassandra-3.0.8.jar:3.0.8]
> 	at org.apache.cassandra.net.IncomingTcpConnection.receiveMessages(IncomingTcpConnection.java:178)
~[apache-cassandra-3.0.8.jar:3.0.8]
> 	at org.apache.cassandra.net.IncomingTcpConnection.run(IncomingTcpConnection.java:92)
~[apache-cassandra-3.0.8.jar:3.0.8]
> {code}
> This trace is from the 3.0.8 node.



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

Mime
View raw message