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 and insert some data on one node, that also works.
I start to insert data on both
What version?
On Fri, Jan 21, 2011 at 9:20 AM, Michael Haspra mhas...@gmail.com 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
Oh sorry:
The version is 0.7.0-beta3-SNAPSHOT
2011/1/21 Jonathan Ellis jbel...@gmail.com
What version?
On Fri, Jan 21, 2011 at 9:20 AM, Michael Haspra mhas...@gmail.com wrote:
Hi all,
I get the following error when I have cassandra running on 2 nodes (I
don't
get it when I start
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
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
