[
https://issues.apache.org/jira/browse/CASSANDRA-5025?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15764515#comment-15764515
]
Pavel S. commented on CASSANDRA-5025:
-------------------------------------
Hi,
Looks like that the issue has not been resolved.
I've just got this:
{code}
15:52:40.194 [cluster1-nio-worker-1] WARN c.d.driver.core.RequestHandler -
/127.0.0.1:9042 replied with server error (java.lang.RuntimeException:
java.util.concurrent.ExecutionException:
org.apache.cassandra.exceptions.ConfigurationException: Column family ID
mismatch (found 5230d9a0-c6cc-11e6-9ece-6d2c86545d91; expected
51d06a20-c6cc-11e6-9ece-6d2c86545d91)), defuncting connection.
{code}
On C* 3.9:
{code}
[cqlsh 5.0.1 | Cassandra 3.9 | CQL spec 3.4.2 | Native protocol v4]
Use HELP for help.
cqlsh>
{code}
with latest driver: "com.datastax.cassandra" % "cassandra-driver-core" %
"3.1.2"}}}
> Schema push/pull race
> ---------------------
>
> Key: CASSANDRA-5025
> URL: https://issues.apache.org/jira/browse/CASSANDRA-5025
> Project: Cassandra
> Issue Type: Bug
> Affects Versions: 1.1.0
> Reporter: Jonathan Ellis
> Assignee: Jonathan Ellis
> Priority: Minor
> Fix For: 1.1.8
>
> Attachments: 5025-v2.txt, 5025-v3.txt, 5025-v4.txt, 5025-v5.txt,
> 5025.txt
>
>
> When a schema change is made, the coordinator pushes the delta to the other
> nodes in the cluster. This is more efficient than sending the entire schema.
> But the coordinator also announces the new schema version, so the other
> nodes' reception of the new version races with processing the delta, and
> usually seeing the new schema wins. So the other nodes also issue a pull to
> the coordinator for the entire schema.
> Thus, schema changes tend to become O(n) in the number of KS and CF present.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
