[
https://issues.apache.org/jira/browse/CASSANDRA-9933?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14647364#comment-14647364
]
Aleksey Yeschenko commented on CASSANDRA-9933:
----------------------------------------------
Unfortunately, the only thing you can do at the moment is avoid concurrent
{{CREATE TABLE}} queries. Don't have clients create tables, have a dedicated
separate step that does. It's a consequence of CASSANDRA-5202, and will
eventually be fixed in CASSANDRA-9424.
For now, try avoiding creating new tables in an automated manner.
> column name mismatch
> --------------------
>
> Key: CASSANDRA-9933
> URL: https://issues.apache.org/jira/browse/CASSANDRA-9933
> Project: Cassandra
> Issue Type: Bug
> Environment: My stack consists of 2 client applications talking to
> same cassandra(2.2.0) instance
> Reporter: shashi ranjan
> Fix For: 2.2.x
>
> Attachments: Screenshot 2015-07-29 16.43.58.png
>
>
> whenever I create a new stack, both client try to create same tables on
> cassandra. But randomly one of the client application fails with following
> exception
> Cassandra error: Cassandra returned error (Server error):
> "java.lang.RuntimeException: java.util.concurrent.ExecutionException:
> org.apache.cassandra.exceptions.ConfigurationException: Column family ID
> mismatch (found c10fb2b0-363b-11e5-9e2b-15fb29128bd7; expected
> c0f721a0-363b-11e5-9e2b-15fb29128bd7)
> PFA: exception from cassandra system logs
> What I can do to prevent this?
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
