cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sylvain Lebresne (Commented) (JIRA)" <>
Subject [jira] [Commented] (CASSANDRA-3884) Intermittent SchemaDisagreementException
Date Thu, 23 Feb 2012 14:12:48 GMT


Sylvain Lebresne commented on CASSANDRA-3884:

+1 with one nit: if I understand correctly Migration.applyImpl() should never return an empty
list of RowMutation, so it would be nice to assert that fact in Migration.apply().

And as said above, I'd prefer separating the test changes to another commit (or open a ticket
for them, but I can live with those change being committed directly).
> Intermittent SchemaDisagreementException
> ----------------------------------------
>                 Key: CASSANDRA-3884
>                 URL:
>             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-v2.patch, 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: 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:!default.jspa
For more information on JIRA, see:


View raw message