[
https://issues.apache.org/jira/browse/CASSANDRA-7566?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14065376#comment-14065376
]
Ben Hood commented on CASSANDRA-7566:
-------------------------------------
OK, so the plot thickens.
By disabling statement preparation in the driver, I was able to workaround this
issue (see this patch for a workaround for this particular test case).
That said, I have noticed that another test fails for a different reason. Now
the test called TestReprepareStatement
(https://github.com/gocql/gocql/blob/master/cassandra_test.go#L582) which tests
the handling of statement re-preparation now fails with this server error:
{noformat}
INFO 18:56:03 Initializing gocql_test.test_reprepare_statement
ERROR 18:56:03 Unexpected exception during request
java.lang.NullPointerException: null
at
org.apache.cassandra.transport.messages.ExecuteMessage.execute(ExecuteMessage.java:105)
~[apache-cassandra-2.1.0-rc3.jar:2.1.0-rc3]
at
org.apache.cassandra.transport.Message$Dispatcher.channelRead0(Message.java:421)
[apache-cassandra-2.1.0-rc3.jar:2.1.0-rc3]
at
org.apache.cassandra.transport.Message$Dispatcher.channelRead0(Message.java:318)
[apache-cassandra-2.1.0-rc3.jar:2.1.0-rc3]
at
io.netty.channel.SimpleChannelInboundHandler.channelRead(SimpleChannelInboundHandler.java:103)
[netty-all-4.0.20.Final.jar:4.0.20.Final]
at
io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:332)
[netty-all-4.0.20.Final.jar:4.0.20.Final]
at
io.netty.channel.AbstractChannelHandlerContext.access$700(AbstractChannelHandlerContext.java:31)
[netty-all-4.0.20.Final.jar:4.0.20.Final]
at
io.netty.channel.AbstractChannelHandlerContext$8.run(AbstractChannelHandlerContext.java:323)
[netty-all-4.0.20.Final.jar:4.0.20.Final]
at
java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
[na:1.8.0_05]
at
org.apache.cassandra.concurrent.AbstractTracingAwareExecutorService$FutureTask.run(AbstractTracingAwareExecutorService.java:162)
[apache-cassandra-2.1.0-rc3.jar:2.1.0-rc3]
at org.apache.cassandra.concurrent.SEPWorker.run(SEPWorker.java:103)
[apache-cassandra-2.1.0-rc3.jar:2.1.0-rc3]
at java.lang.Thread.run(Thread.java:745) [na:1.8.0_05]
{noformat}
This looks like two different bugs and potentially should be handled by two
separate bug reports?
> DROP/CREATE TABLE cycle causes unrecognized column family
> ---------------------------------------------------------
>
> Key: CASSANDRA-7566
> URL: https://issues.apache.org/jira/browse/CASSANDRA-7566
> Project: Cassandra
> Issue Type: Bug
> Components: Core
> Environment: OSX 10.9.4 / JDK 1.8.0_05
> Reporter: Ben Hood
> Assignee: Yuki Morishita
>
> An integration test suite that drops and creates the same column family 3
> times causes the following error in the server log:
> INFO 15:40:34 Initializing gocql_test.wiki_page
> ERROR 15:40:34 Attempted to write commit log entry for unrecognized column
> family: b0e167e0-0dc8-11e4-9cbb-29a4872887f2
> ERROR 15:40:34 Attempting to mutate non-existant column family
> b0e167e0-0dc8-11e4-9cbb-29a4872887f2
> ERROR 15:40:34 Attempted to write commit log entry for unrecognized column
> family: b0e167e0-0dc8-11e4-9cbb-29a4872887f2
> ERROR 15:40:34 Attempting to mutate non-existant column family
> b0e167e0-0dc8-11e4-9cbb-29a4872887f2
> The test that reproduces this issue is here:
> https://github.com/gocql/gocql/blob/master/wiki_test.go
> Interestingly this issue only occurs after the common table is
> dropped/created for the 3rd time. If only one of the tests is run on its own,
> this issue does not arise.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
