[jira] [Commented] (CASSANDRA-7566) DROP/CREATE TABLE cycle causes unrecognized column family
[ https://issues.apache.org/jira/browse/CASSANDRA-7566?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14065459#comment-14065459 ] Tyler Hobbs commented on CASSANDRA-7566: The NPE in ExecuteMessage is CASSANDRA-7454. That was supposed to be fixed in rc3, but it looks like it got committed for 2.1.1 instead. I'll commit that to 2.1.0 and update the ticket. > 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)
[jira] [Commented] (CASSANDRA-7566) DROP/CREATE TABLE cycle causes unrecognized column family
[ https://issues.apache.org/jira/browse/CASSANDRA-7566?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14065383#comment-14065383 ] Ben Hood commented on CASSANDRA-7566: - For anybody coming across this issue via Google, the original pull request to gocql that provokes this error is here: https://github.com/gocql/gocql/pull/198 > 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)
[jira] [Commented] (CASSANDRA-7566) DROP/CREATE TABLE cycle causes unrecognized column family
[
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)
[jira] [Commented] (CASSANDRA-7566) DROP/CREATE TABLE cycle causes unrecognized column family
[ https://issues.apache.org/jira/browse/CASSANDRA-7566?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14065343#comment-14065343 ] Ben Hood commented on CASSANDRA-7566: - [~yukim] Yes, gocql does prepare all statements by default. I could see if I can disable this behavior in the gocql driver and see if that has an effect. > 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)
[jira] [Commented] (CASSANDRA-7566) DROP/CREATE TABLE cycle causes unrecognized column family
[ https://issues.apache.org/jira/browse/CASSANDRA-7566?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14065136#comment-14065136 ] Yuki Morishita commented on CASSANDRA-7566: --- [~0x6e6562], does gocql use prepared statement? I'm guessing we need to drop prepared statement too when dropping columnfamily. > 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)
[jira] [Commented] (CASSANDRA-7566) DROP/CREATE TABLE cycle causes unrecognized column family
[ https://issues.apache.org/jira/browse/CASSANDRA-7566?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14065090#comment-14065090 ] Ben Hood commented on CASSANDRA-7566: - The CQL that is submitted in this test is: DROP TABLE IF EXISTS wiki_page; followed by CREATE TABLE wiki_page (...); So I'm not seeing why this should result in a server error. Also, this is not just an entry in the server log file, it causes a test to fail that passes on our Travis run for the 2.0.6 and 2.0.7 releases. > 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)
[jira] [Commented] (CASSANDRA-7566) DROP/CREATE TABLE cycle causes unrecognized column family
[ https://issues.apache.org/jira/browse/CASSANDRA-7566?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14065089#comment-14065089 ] Brandon Williams commented on CASSANDRA-7566: - bq. CASSANDRA-5202 appears to have been fixed in 2.1 beta1, but the version I'm using is 2.1-rc3. Is 2.1 beta 1 a newer release than 2.1-rc3? No; my mistake. Sorry. > 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)
[jira] [Commented] (CASSANDRA-7566) DROP/CREATE TABLE cycle causes unrecognized column family
[ https://issues.apache.org/jira/browse/CASSANDRA-7566?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14065081#comment-14065081 ] Yuki Morishita commented on CASSANDRA-7566: --- CommitLog just writes log in ERROR when it detects dropped CF(https://github.com/apache/cassandra/blob/cassandra-2.1.0-rc3/src/java/org/apache/cassandra/db/commitlog/CommitLogSegment.java#L439). Should it be changed to WARN or INFO? > 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)
[jira] [Commented] (CASSANDRA-7566) DROP/CREATE TABLE cycle causes unrecognized column family
[ https://issues.apache.org/jira/browse/CASSANDRA-7566?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14065075#comment-14065075 ] Ben Hood commented on CASSANDRA-7566: - CASSANDRA-5202 appears to have been fixed in 2.1 beta1, but the version I'm using is 2.1-rc3. Is 2.1 beta 1 a newer release than 2.1-rc3? > 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)
