cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jonathan Ellis (Commented) (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-3884) Intermittent SchemaDisagreementException
Date Sat, 11 Feb 2012 20:30:59 GMT

    [ https://issues.apache.org/jira/browse/CASSANDRA-3884?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13206253#comment-13206253
] 

Jonathan Ellis commented on CASSANDRA-3884:
-------------------------------------------

If you mean you can race inserts into the new CF, with the CF creation, then sure, there's
no way we can make that work.  But all the other CFs should be fine.
                
> 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

        

Mime
View raw message