Thanks Erick I think there is no problem with schema version:
At 2020-04-04 10:35:06, "Erick Ramirez" <erick.rami...@datastax.com> wrote: The symptoms in your post indicate that you have a schema disagreement in your cluster which you need to resolve. These 2 nodes in particular are the ones you need to investigate in the first place: [2020-04-03 20:07:44,242] Got negative replies from endpoints [10.17.140.69, 10.17.140.59] If you run nodetool describecluster on several nodes, it will likely indicate that the 2 nodes above are unreachable. You need to review the logs to determine the cause and the quickest workaround is to restart those 2 nodes. It is also the likely reason you were getting the "unconfigured table" error, i.e. the node doesn't know about that table. CF ID b979fcc0-75a3-11ea-a277-bdf3d1289bdd indicates the table was created earlier today (April 3 05:07:44 PT) and the table's schema didn't get propagated to all the nodes in the cluster hence the schema disagreement. Cheers! GOT QUESTIONS? Apache Cassandra experts from the community and DataStax have answers! Share your expertise on https://community.datastax.com/.
