Hello, dlu66061. A common issue with schema disagreements is time drift on the nodes. Are you using NTP?
The only other issue is when the nodes are not reachable at the time that the schema update was being propagated --- http://www.datastax.com/documentation/cassandra/2.0/cassandra/dml/dml_handle_schema_disagree_t.html You should be able to see propagation by MigrationStage in the system.log by grepping for the the schema UUID that is listed in "nodetool describecluster". Depending on the state of the node that didn't get the update, you could have also tried "nodetool resetlocalschema" which effectively deletes the schema metadata on that node and forces it to get a copy from one of the other nodes. Cheers, Erick
