[
https://issues.apache.org/jira/browse/CASSANDRA-5025?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13510914#comment-13510914
]
Pavel Yaskevich commented on CASSANDRA-5025:
--------------------------------------------
[~cherro] I don't think that we every want to make such a frequent schema
changes, it's not considered a good practice for a number of reasons, unless
you are trying to do something like temp-tables which has it's own
implications... Agree on [~jbellis] that it doesn't seem like a good idea to
re-invent HH for schema until we have a good reason to do so.
> Schema push/pull race
> ---------------------
>
> Key: CASSANDRA-5025
> URL: https://issues.apache.org/jira/browse/CASSANDRA-5025
> Project: Cassandra
> Issue Type: Bug
> Components: Core
> Affects Versions: 1.1.0
> Reporter: Jonathan Ellis
> Assignee: Jonathan Ellis
> Priority: Minor
> Fix For: 1.1.8
>
> Attachments: 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 is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
