We have similar exception before, and the root cause was like Aaron
mentioned.
You will encounter this exception If you have code create CF on the fly and
data was insert into the node which hasn't got schema synced yet.
You will have to call describe_schema_version() to ensure all nodes has
Hi All,
Could you please help me understand the impact on my data?
I am running a 6 node 0.7-rc4 Cassandra cluster with RF=2. Schema was defined
when the cluster was created and did not change. I am doing batch load with
CL=ONE. The cluster is under some stress in memory and I/O. Each node has
Sounds like there are multiple versions of your schema around the cluster. What client API are you using? Does it support thedescribe_schema_versions() function? This will tell you how many versions there are.The easy solutions here is scrub the data and start a new 0.7 cluster using the release
