[
https://issues.apache.org/jira/browse/CASSANDRA-1403?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12899594#action_12899594
]
Stu Hood commented on CASSANDRA-1403:
-------------------------------------
+1
I expect that cfId generation is going to need to change significantly to allow
for concurrent schema changes.
> CFMetaData id gets out of sync
> ------------------------------
>
> Key: CASSANDRA-1403
> URL: https://issues.apache.org/jira/browse/CASSANDRA-1403
> Project: Cassandra
> Issue Type: Bug
> Components: Core
> Affects Versions: 0.7 beta 1
> Reporter: Gary Dusbabek
> Assignee: Gary Dusbabek
> Fix For: 0.7 beta 2
>
> Attachments: v0-0001-fix-max-id-after-adding-a-column-family.txt
>
>
> stand up two nodes.
> load a KS + cf on A.
> add another CF on A.
> Let the cluster quiesce.
> add a CF on B.
> You get the out of sync error. I'm pretty sure this is because
> AddColumnFamily doesn't CFM.fixMaxId() like AddKeyspace does.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
