I am having trouble with keyspace creation/replication when adding a brisk node to an existing cassandra cluster.
I moved the brisk.jar into the lib folder of the cassandra nodes, and modified the yaml file to use the brisk simple snitch.
The cluster comes up fine with all nodes in the cluster and schemas in agreement. The brisk version of nodetool, shows the correct nodes in brisk dc and cassandra dc.
When creating a new keyspace, it says it can't reach the other node and then after a short pause a message about schemas agree. However, when you describe the cluster there is now a different schema version for each node.
I don't have this problem when I start the vanilla cassandra node as the 0.8.1 version that comes with the brisk package.
Are there configuration changes I have missed to add a brisk node running 0.8.1 to an existing cassandra cluster running 0.8.0.
Here is the output from the system.log on the Brisk node. This keyspace was created on the vanilla cassandra node.
ERROR [Thread-47] 2011-06-24 11:00:09,002 AbstractCassandraDaemon.java (line 113) Fatal exception in thread Thread[Thread-47,5,main]
java.lang.AssertionError: No stage for message type null