Re: java.lang.AssertionError: Memory was freed during index rebuild

2018-10-24 Thread Jeff Jirsa
3.5 is probably not a version you should be using in production in 2018 - it was a feature release and has had no bug fixes for years. Going up to 3.11.3 will likely fix many serious bugs you’re not noticing, and maybe the bug below you are noticing -- Jeff Jirsa > On Oct 24, 2018, at 5:03

Re: java.lang.AssertionError in cqlsh

2014-12-11 Thread Chamila Wijayarathna
Done. https://issues.apache.org/jira/browse/CASSANDRA-8461 On Thu, Dec 11, 2014 at 9:00 PM, Philip Thompson < philip.thomp...@datastax.com> wrote: > That is definitely a bug, and I do not see a JIRA with the same problem > already filed. Could you file an issue please? Cassandra - ASF JIRA >

Re: java.lang.AssertionError in cqlsh

2014-12-11 Thread Tyler Hobbs
It looks like this is resolved in the latest 2.1. I think the fix was a combination of CASSANDRA-8286 and something else. On Thu, Dec 11, 2014 at 9:30 AM, Philip Thompson < philip.thomp...@datastax.com> wrote: > That is definitely a bug, and

Re: java.lang.AssertionError in cqlsh

2014-12-11 Thread Philip Thompson
That is definitely a bug, and I do not see a JIRA with the same problem already filed. Could you file an issue please? Cassandra - ASF JIRA On Thu, Dec 11, 2014 at 10:15 AM, Chamila Wijayarathna < cdwijayarat...@gmail.com> wrote:

Re: java.lang.AssertionError in cqlsh

2014-12-11 Thread Chamila Wijayarathna
Hi Philip, I'm using version 2.1.2. Following is the error log at system.log. ( https://gist.github.com/cdwijayarathna/2749f52c52f5c7fd807d ) ERROR [SharedPool-Worker-1] 2014-12-11 20:42:20,152 Message.java:538 - Unexpected exception during request; channel = [id: 0xea57d8b6, / 127.0.0.1:35624 =

Re: java.lang.AssertionError in cqlsh

2014-12-11 Thread Philip Thompson
The full error should be in that node's system.log file. What version are you running? On Thu, Dec 11, 2014 at 9:42 AM, Chamila Wijayarathna < cdwijayarat...@gmail.com> wrote: > Hi Philip, > > I ran my queries on cqlsh terminal and it only shows this. > > Thank you! > > On Thu, Dec 11, 2014 at 6:

Re: java.lang.AssertionError in cqlsh

2014-12-11 Thread Chamila Wijayarathna
Hi Philip, I ran my queries on cqlsh terminal and it only shows this. Thank you! On Thu, Dec 11, 2014 at 6:43 PM, Philip Thompson < philip.thomp...@datastax.com> wrote: > There is a definitely a problem here, but without the entire stack trace, > it is unclear what exactly may be wrong. > > On

Re: java.lang.AssertionError in cqlsh

2014-12-11 Thread Philip Thompson
There is a definitely a problem here, but without the entire stack trace, it is unclear what exactly may be wrong. On Thu, Dec 11, 2014 at 7:37 AM, Chamila Wijayarathna < cdwijayarat...@gmail.com> wrote: > Hello all, > > I have a column family with following schema. > > CREATE TABLE corpus.trigra

Re: java.lang.AssertionError on starting the node

2013-06-04 Thread himanshu.joshi
Hi, I deleted a column family from the keyspace and the error has gone now. Thanks for the reply. -- Thanks & Regards, Himanshu Joshi On 05/31/2013 08:16 PM, S C wrote: What was the node doing right before the ERROR? Can you post some more log? Thanks, SC --

RE: java.lang.AssertionError on starting the node

2013-05-31 Thread S C
What was the node doing right before the ERROR? Can you post some more log? Thanks,SC Date: Fri, 31 May 2013 10:57:38 +0530 From: himanshu.jo...@orkash.com To: user@cassandra.apache.org Subject: java.lang.AssertionError on starting the node Hi, I have created a 2 nod

RE: java.lang.AssertionError

2012-01-05 Thread Michael Vaknine
Thanks Aaron. Michael From: aaron morton [mailto:aa...@thelastpickle.com] Sent: Wednesday, January 04, 2012 10:06 PM To: user@cassandra.apache.org Subject: Re: java.lang.AssertionError Will be fixed in 1.0.7 https://issues.apache.org/jira/browse/CASSANDRA-3656 Cheers

Re: java.lang.AssertionError

2012-01-04 Thread aaron morton
Will be fixed in 1.0.7 https://issues.apache.org/jira/browse/CASSANDRA-3656 Cheers - Aaron Morton Freelance Developer @aaronmorton http://www.thelastpickle.com On 4/01/2012, at 11:26 PM, Michael Vaknine wrote: > Hi, > > I have a 4 cluster version 1.0.3 which was upgraded from

Re: java.lang.AssertionError in MessagingService.receive during heavy write.

2011-01-21 Thread Michael Haspra
It seams that this error was caused by an extension sending wrong messages around, so that Message.getMessageType(). would return null since the verb was not known to cassandra. Unfortunately I couldn't tell from the error. But upgrading would be a good idea anyway... 2011/1/21 Jonathan Ellis >

Re: java.lang.AssertionError in MessagingService.receive during heavy write.

2011-01-21 Thread Jonathan Ellis
I don't see an assert in current 0.7 MessagingService that looks like a candidate for that. So it's probably fixed. Since apparently you're comfortable running snapshot builds, I'd upgrade to the latest 0.7 branch. At least then you'd be running into new bugs and not two month old ones. On Fri,

Re: java.lang.AssertionError in MessagingService.receive during heavy write.

2011-01-21 Thread Michael Haspra
Oh sorry: The version is 0.7.0-beta3-SNAPSHOT 2011/1/21 Jonathan Ellis > What version? > > On Fri, Jan 21, 2011 at 9:20 AM, Michael Haspra wrote: > > Hi all, > > > > I get the following error when I have cassandra running on 2 nodes (I > don't > > get it when I start only one node). > > > >

Re: java.lang.AssertionError in MessagingService.receive during heavy write.

2011-01-21 Thread Jonathan Ellis
What version? On Fri, Jan 21, 2011 at 9:20 AM, Michael Haspra wrote: > Hi all, > > I get the following error when I have cassandra running on 2 nodes (I don't > get it when I start only one node). > > The startup on both nodes seems to be fine (e.g no error messages). > Then I set up a keyspace a