Re: C* 2.1-rc2 gets unstable after a 'DROP KEYSPACE' command ?

2014-08-07 Thread Fabrice Larcher
Hello, After a 'DROP TABLE' command that returns errors={}, last_host=127.0.0.1 (like most DROP commands do) from CQLSH with C* 2.1.0-rc2, I stopped C*. And I can not start one node. It says : ERROR 09:18:34 Exception encountered during startup java.lang.NullPointerException: null at

Re: C* 2.1-rc2 gets unstable after a 'DROP KEYSPACE' command ?

2014-08-07 Thread Sylvain Lebresne
It would be nice if you can try with 2.1.0-rc5 (there has been quite a bit of bug fixes since rc2). If you can still reproduce that NPE there, please do open a jira ticket with the reproduction steps. On Thu, Aug 7, 2014 at 11:29 AM, Fabrice Larcher fabrice.larc...@level5.fr wrote: Hello,

Re: C* 2.1-rc2 gets unstable after a 'DROP KEYSPACE' command ?

2014-07-17 Thread Benedict Elliott Smith
Also https://issues.apache.org/jira/browse/CASSANDRA-7437 and https://issues.apache.org/jira/browse/CASSANDRA-7465 for rc3, although the CounterCacheKey assertion looks like an independent (though comparatively benign) bug I will file a ticket for. Can you try this against rc3 to see if the

Re: C* 2.1-rc2 gets unstable after a 'DROP KEYSPACE' command ?

2014-07-17 Thread Fabrice Larcher
Hello, I still experience a similar issue after a 'DROP KEYSPACE' command with C* 2.1-rc3. Connection to the node may fail after a 'DROP'. But I did not see this issue with 2.1-rc1 (- it seems like to be a regression brought with 2.1-rc2). Fabrice LARCHER 2014-07-17 9:19 GMT+02:00 Benedict

Re: C* 2.1-rc2 gets unstable after a 'DROP KEYSPACE' command ?

2014-07-16 Thread Tyler Hobbs
This looks like https://issues.apache.org/jira/browse/CASSANDRA-6959, but that was fixed for 2.1.0-rc1. Is there any chance you can put together a script to reproduce the issue? On Thu, Jul 10, 2014 at 8:51 AM, Pavel Kogan pavel.ko...@cortica.com wrote: It seems that memtable tries to flush

C* 2.1-rc2 gets unstable after a 'DROP KEYSPACE' command ?

2014-07-10 Thread Fabrice Larcher
​Hello, I am using the 'development' version 2.1-rc2. With one node (=localhost), I get timeouts trying to connect to C* after running a 'DROP KEYSPACE' command. I have following error messages in system.log : INFO [SharedPool-Worker-3] 2014-07-09 16:29:36,578 MigrationManager.java:319 - Drop

Re: C* 2.1-rc2 gets unstable after a 'DROP KEYSPACE' command ?

2014-07-10 Thread Pavel Kogan
It seems that memtable tries to flush itself to SSTable of not existing keyspace. I don't know why it is happens, but probably running nodetool flush before drop should prevent this issue. Pavel On Thu, Jul 10, 2014 at 4:09 AM, Fabrice Larcher fabrice.larc...@level5.fr wrote: ​Hello, I am