[
https://issues.apache.org/jira/browse/CASSANDRA-3884?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13206087#comment-13206087
]
Pavel Yaskevich commented on CASSANDRA-3884:
--------------------------------------------
The first rule of the schema migration (which you have violated) is to make
sure that cluster is reasonably quiet for KS/CF you do updates upon because
different bad things can happen if you migrate under heavy load. Can you please
attach to the ticket system.log from both nodes in the situation when you get
SchemaDisagreementException?
> Intermittent SchemaDisagreementException
> ----------------------------------------
>
> Key: CASSANDRA-3884
> URL: https://issues.apache.org/jira/browse/CASSANDRA-3884
> Project: Cassandra
> Issue Type: Bug
> Components: Core
> Affects Versions: 1.1.0
> Environment: using ccm on ubuntu.
> Reporter: Tyler Patterson
> Assignee: Pavel Yaskevich
>
> Set up a cluster of two nodes (on cassandra-1.1), create some keyspaces and
> column families, and then make several schema changes. Everything is being
> done through only one of the nodes. About once every 10 times (on my setup)
> I get a SchemaDisagreementException when creating and dropping keyspaces.
> There is a dtest for this: schema_changes_test.py. If your environment
> behaves like mine, you might need to run it 10 times to get the error.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
