cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sylvain Lebresne (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (CASSANDRA-5904) Don't announce schema version until we've loaded the changes locally
Date Tue, 20 Aug 2013 10:24:55 GMT

     [ https://issues.apache.org/jira/browse/CASSANDRA-5904?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Sylvain Lebresne updated CASSANDRA-5904:
----------------------------------------

    Attachment: 5904.txt

Attaching trivial patch that moves the call to updateVersionAndAnnounce at the end of mergeSchema.
                
> Don't announce schema version until we've loaded the changes locally
> --------------------------------------------------------------------
>
>                 Key: CASSANDRA-5904
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-5904
>             Project: Cassandra
>          Issue Type: Bug
>            Reporter: Sylvain Lebresne
>            Assignee: Sylvain Lebresne
>            Priority: Minor
>             Fix For: 1.2.9
>
>         Attachments: 5904.txt
>
>
> Currently, we call updateSchemaAndAnnounce (which sets the schema version in the system
table and announce it on gossip) in DefsTable.mergeSchema as soon as we've persisted the schema
mutation but *before* we've actually loaded new/updated KS/CF locally. This makes it impossible
to reliably check for schema agreement in a cluster as even if all nodes have the same version
set in the system tables, you could still get an insert on a new table rejected because the
table hasn't been loaded yet.

--
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

Mime
View raw message