[
https://issues.apache.org/jira/browse/CASSANDRA-1824?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12971451#action_12971451
]
Gary Dusbabek commented on CASSANDRA-1824:
------------------------------------------
Here is how things broke:
1. Node 2 starts up and is fed a schema. it then includes SCHEMA in its gossip
state as part of *applying the migration.*
2. Node 2 is restarted. It no longer includes SCHEMA in its gossip state.
3. Start any number of nodes. None of them will get schema.
The fix puts SCHEMA in the gossip state every time schema is announced.
> Schema only fully propagates from seeds
> ---------------------------------------
>
> Key: CASSANDRA-1824
> URL: https://issues.apache.org/jira/browse/CASSANDRA-1824
> Project: Cassandra
> Issue Type: Bug
> Affects Versions: 0.7 beta 1
> Reporter: Brandon Williams
> Assignee: Gary Dusbabek
> Fix For: 0.7.0
>
> Attachments: v2-0001-always-put-schema-state-in-local-gossip.txt
>
>
> If you have nodes X, Y, and Z, and Y already has some schema, but X and Z do
> not, and X is the seed node for the cluster, X will pick up the schema from
> Y, but it will never propagate to Z. If X has the schema, it will propagate
> to both Y and Z.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
