> > Stupid question, but how do I find the problem table? The error message > complains about a keyspace (by uuid); I haven't seen errors relating to a > specific table. I've poked around in the data directory, but I'm not sure > what I'm looking for.
Is the message complaining about a *keyspace* or abou*t a table (cfid)*? You'r original was complaining about a table: at=IncomingTcpConnection.run UnknownColumnFamilyException reading from > socket; closing org.apache.cassandra.db.UnknownColumnFamilyException: > Couldn't find *cfId=3ecce750-84d3-11e5-bdd9-**dd7717dcdbd5* All the best, [image: datastax_logo.png] <http://www.datastax.com/> Sebastián Estévez Solutions Architect | 954 905 8615 | sebastian.este...@datastax.com [image: linkedin.png] <https://www.linkedin.com/company/datastax> [image: facebook.png] <https://www.facebook.com/datastax> [image: twitter.png] <https://twitter.com/datastax> [image: g+.png] <https://plus.google.com/+Datastax/about> <http://feeds.feedburner.com/datastax> <http://goog_410786983> <http://www.datastax.com/gartner-magic-quadrant-odbms> DataStax is the fastest, most scalable distributed database technology, delivering Apache Cassandra to the world’s most innovative enterprises. Datastax is built to be agile, always-on, and predictably scalable to any size. With more than 500 customers in 45 countries, DataStax is the database technology and transactional backbone of choice for the worlds most innovative companies such as Netflix, Adobe, Intuit, and eBay. On Wed, Nov 11, 2015 at 12:26 PM, Maciek Sakrejda <mac...@heroku.com> wrote: > On Tue, Nov 10, 2015 at 3:20 PM, Sebastian Estevez < > sebastian.este...@datastax.com> wrote: > >> #1 The cause of this problem is a CREATE TABLE statement collision. Do not >> generate tables >> dynamically from multiple clients, even with IF NOT EXISTS. First thing you >> need to do is >> fix your code so that this does not happen. Just create your tables manually >> from cqlsh allowing >> time for the schema to settle. >> >> #2 Here's the fix: >> >> 1) Change your code to not automatically re-create tables (even with IF NOT >> EXISTS). >> >> 2) Run a rolling restart to ensure schema matches across nodes. Run nodetool >> describecluster >> >> around your cluster. Check that there is only one schema version. >> >> Thanks, that seems to have resolved the schema version inconsistency > (though I'm still getting the original error). > >> ON EACH NODE: >> >> 3) Check your filesystem and see if you have two directories for the table in >> >> question in the data directory. >> >> Stupid question, but how do I find the problem table? The error message > complains about a keyspace (by uuid); I haven't seen errors relating to a > specific table. I've poked around in the data directory, but I'm not sure > what I'm looking for. > >
