cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Tyler Hobbs (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-12192) dtest failure in upgrade_tests.cql_tests.TestCQLNodes3RF3_Upgrade_current_3_0_x_To_head_trunk.map_keys_indexing_test
Date Thu, 11 Aug 2016 22:23:20 GMT

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

Tyler Hobbs commented on CASSANDRA-12192:
-----------------------------------------

It looks like the truncate _does_ happen successfully on all nodes, but the response from
the upgraded node to the old node doesn't get through.  This appears to be caused by this
schema change:

{noformat}
if is_upgraded:
    if self.get_node_version(is_upgraded) >= '3.0':
        cursor.execute("CREATE INDEX ON test(m)")
    else:
        assert_invalid(cursor, "CREATE INDEX on test(m)")
{noformat}

When that schema change is removed, all of the truncates complete successfully.  I'm guessing
what happens is that the schema change in a mixed-version cluster puts the old node in a state
where it doesn't correctly handle the truncate message from the upgraded node.  I'll look
into this more, but it does seem like this is a case where we should adjust the test to not
perform an unsupported operation (schema change in a mixed cluster) and expect everything
to work correctly afterwards.

> dtest failure in upgrade_tests.cql_tests.TestCQLNodes3RF3_Upgrade_current_3_0_x_To_head_trunk.map_keys_indexing_test
> --------------------------------------------------------------------------------------------------------------------
>
>                 Key: CASSANDRA-12192
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-12192
>             Project: Cassandra
>          Issue Type: Bug
>            Reporter: Sean McCarthy
>            Assignee: Tyler Hobbs
>              Labels: dtest
>         Attachments: node1.log, node1_debug.log, node1_gc.log, node2.log, node2_debug.log,
node2_gc.log, node3.log, node3_debug.log, node3_gc.log
>
>
> example failure:
> http://cassci.datastax.com/job/upgrade_tests-all/59/testReport/upgrade_tests.cql_tests/TestCQLNodes3RF3_Upgrade_current_3_0_x_To_head_trunk/map_keys_indexing_test
> Failed on CassCI build upgrade_tests-all #59
> {code}
> Stacktrace
>   File "/usr/lib/python2.7/unittest/case.py", line 329, in run
>     testMethod()
>   File "/home/automaton/cassandra-dtest/tools.py", line 290, in wrapped
>     f(obj)
>   File "/home/automaton/cassandra-dtest/upgrade_tests/cql_tests.py", line 3668, in map_keys_indexing_test
>     cursor.execute("TRUNCATE test")
>   File "cassandra/cluster.py", line 1941, in cassandra.cluster.Session.execute (cassandra/cluster.c:33642)
>     return self.execute_async(query, parameters, trace, custom_payload, timeout, execution_profile).result()
>   File "cassandra/cluster.py", line 3629, in cassandra.cluster.ResponseFuture.result
(cassandra/cluster.c:69369)
>     raise self._final_exception
> '<Error from server: code=1003 [Error during truncate] message="Error during truncate:
Truncate timed out - received only 2 responses">
> {code}
> Related failure: 
> http://cassci.datastax.com/job/upgrade_tests-all/59/testReport/upgrade_tests.cql_tests/TestCQLNodes2RF1_Upgrade_current_3_0_x_To_head_trunk/map_keys_indexing_test/



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

Mime
View raw message