[ https://issues.apache.org/jira/browse/CASSANDRA-3884?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Pavel Yaskevich updated CASSANDRA-3884: --------------------------------------- Attachment: CASSANDRA-3884.patch I have localized and fixed the problem which was that coordinator wasn't sending the mutations used to change schema but a snapshot of the schema itself after each of the migrations. > 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 > Fix For: 1.1.0 > > Attachments: CASSANDRA-3884.patch > > > 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