> > I have had that error sometimes when schema mismatch but also when all > schema match. So I think this is not the only cause. > Have you checked the logs for errors on 135.181.222.100, 135.181.217.109, and 135.181.221.180? They may give you some better information about why they are sending bad replies.
By the way, what could cause such a shema mismatch. I would like to know > what should be or not be done in order to keep schema agreements between > nodes? Are there some mistakes to avoid in table design to prevent such > issue? > Schema changes aren't strongly consistent across the cluster, so they can occur through various problems. The main one would be multiple clients making schema changes simultaneously and separate nodes ending up with conflicting schema definitions. Best practice to avoid that is to only make schema changes from a single client. -- raft.so - Cassandra consulting, support, and managed services
