cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jonathan Ellis (JIRA)" <>
Subject [jira] Commented: (CASSANDRA-1389) Schema migrations are noisy
Date Wed, 18 Aug 2010 15:02:16 GMT


Jonathan Ellis commented on CASSANDRA-1389:

So the coordinator node is the only one that does announce now?  That should be fine as long
as we're not only relying on gossip, which is too slow for a good user experience imo.

> Schema migrations are noisy
> ---------------------------
>                 Key: CASSANDRA-1389
>                 URL:
>             Project: Cassandra
>          Issue Type: Improvement
>          Components: Core
>    Affects Versions: 0.7 beta 1
>            Reporter: Gary Dusbabek
>            Assignee: Gary Dusbabek
>            Priority: Minor
>             Fix For: 0.7 beta 2
>         Attachments: v1-0001-do-not-announce-when-applying-schema-updates-that-arri.txt
> Currently, when a schema update happens on a node, it calls Migration.announce(), which
sends a message to every live node announcing its version.  This creates a terrible amount
of noise (n^2 messages) in fairly rapid succession.
> I think announcing should only be done as part of a) a client request or b) loadSchemaFromYaml.
 All other migrations (as a result of receiving a message) should just keep quiet after applying
the migration.

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message