We have a 5-node Cassandra cluster with a single 1.0.9 installation and four 1.0.6 installations.
After bringing up 1.1.4 there are no errors in the log, but the cluster now suffers from schema disagreement
[default@unknown] describe cluster;
59adb24e-f3cd-3e02-97f0-5b395827453f: [10.10.29.67] <- The new 1.1.4 node
943fc0a0-f678-11e1-0000-339cf8a6c1bf: [10.10.87.228, 10.10.153.45, 10.10.145.90, 10.38.127.80] <- nodes in the old cluster
The recipe for recovering from schema disagreement (http://wiki.apache.org/cassandra/FAQ#schema_disagreement
) doesn't cover the new directory layout. The system/Schema directory is empty save for a snapshots subdirectory. system/schema_columnfamilies and system/schema_keyspaces contain some files. As described in datastax's description, we tried running nodetool upgradesstables. When this had done, describe schema in the cli showed a schema definition which seemed correct, but was indeed different from the schema on the other nodes in the cluster.
Any clues on how we should proceed?