You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Gary Dusbabek (JIRA)" <ji...@apache.org> on 2010/08/18 16:48:17 UTC
[jira] Updated: (CASSANDRA-1389) Schema migrations are noisy
[ https://issues.apache.org/jira/browse/CASSANDRA-1389?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Gary Dusbabek updated CASSANDRA-1389:
-------------------------------------
Attachment: v1-0001-do-not-announce-when-applying-schema-updates-that-arri.txt
> Schema migrations are noisy
> ---------------------------
>
> Key: CASSANDRA-1389
> URL: https://issues.apache.org/jira/browse/CASSANDRA-1389
> 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.