[ https://issues.apache.org/jira/browse/CASSANDRA-12834?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Sylvain Lebresne updated CASSANDRA-12834: ----------------------------------------- Reviewer: Sam Tunnicliffe Fix Version/s: 3.11 3.0.11 Status: Patch Available (was: Open) This doesn't really reproduce locally but given the error message, and give the file in question has 2 different test that name their index {{c_index}}, I believe this is a relatively simple name clash. Especially since while both test will clean after themselves, that cleaning is done asynchronously (the table used by the test is different, so the asynchronous part is not supposed to be an issue, but index names are checked for conflict globally), which also explain why this is an intermittent failure. Assuming I'm correct, as one of those test don't really use the name of the index, the simplest fix is to just remove the name on that test, letting the index name being generated automatically. That trivial fix is [here|https://github.com/pcmanus/cassandra/commit/60f9949d6ddafd87f26e1157d0e3c5b28a08f552]. I tested this locally (to make doubly sure the test was indeed not relying on the index name) but I don't feel it's worth wasting CI ressource on this, unless someone has an issue with that. Also, the patch is on trunk since that where the report is from, but it seems this should be fixed from 3.0 onwards, so I'll commit there if we're good with the patch. Putting [~beobal] as reviewer since he originated the test (not that the fix require any particular expertise on the test itself). > testall failure in > org.apache.cassandra.index.internal.CassandraIndexTest.indexOnFirstClusteringColumn > ------------------------------------------------------------------------------------------------------ > > Key: CASSANDRA-12834 > URL: https://issues.apache.org/jira/browse/CASSANDRA-12834 > Project: Cassandra > Issue Type: Bug > Reporter: Sean McCarthy > Assignee: Sylvain Lebresne > Labels: test-failure > Fix For: 3.0.11, 3.11 > > > example failure: > http://cassci.datastax.com/job/trunk_testall/1250/testReport/org.apache.cassandra.index.internal/CassandraIndexTest/indexOnFirstClusteringColumn/ > {code} > Error Message > Error setting schema for test (query was: CREATE INDEX c_index ON > cql_test_keyspace.table_20(c)) > {code}{code} > Stacktrace > java.lang.RuntimeException: Error setting schema for test (query was: CREATE > INDEX c_index ON cql_test_keyspace.table_20(c)) > at org.apache.cassandra.cql3.CQLTester.schemaChange(CQLTester.java:705) > at org.apache.cassandra.cql3.CQLTester.createIndex(CQLTester.java:627) > at > org.apache.cassandra.index.internal.CassandraIndexTest.access$400(CassandraIndexTest.java:56) > at > org.apache.cassandra.index.internal.CassandraIndexTest$TestScript.run(CassandraIndexTest.java:626) > at > org.apache.cassandra.index.internal.CassandraIndexTest.indexOnFirstClusteringColumn(CassandraIndexTest.java:86) > Caused by: org.apache.cassandra.exceptions.InvalidRequestException: Index > c_index already exists > at > org.apache.cassandra.cql3.statements.CreateIndexStatement.validate(CreateIndexStatement.java:133) > at org.apache.cassandra.cql3.CQLTester.schemaChange(CQLTester.java:696) > {code} -- This message was sent by Atlassian JIRA (v6.3.4#6332)