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/17 22:33:16 UTC
[jira] Created: (CASSANDRA-1403) CFMetaData id gets out of sync
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
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.
[jira] Commented: (CASSANDRA-1403) CFMetaData id gets out of sync
Posted by "Gary Dusbabek (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-1403?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12899603#action_12899603 ]
Gary Dusbabek commented on CASSANDRA-1403:
------------------------------------------
It will need to act like a distributed counter.
> 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.
[jira] Commented: (CASSANDRA-1403) CFMetaData id gets out of sync
Posted by "Hudson (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-1403?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12899836#action_12899836 ]
Hudson commented on CASSANDRA-1403:
-----------------------------------
Integrated in Cassandra #517 (See [https://hudson.apache.org/hudson/job/Cassandra/517/])
fix max id after adding a column family. patch by gdusbabek, reviewed by stuhood. CASSANDRA-1403
> 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.
[jira] Commented: (CASSANDRA-1403) CFMetaData id gets out of sync
Posted by "Stu Hood (JIRA)" <ji...@apache.org>.
[ 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.
[jira] Updated: (CASSANDRA-1403) CFMetaData id gets out of sync
Posted by "Gary Dusbabek (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-1403?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Gary Dusbabek updated CASSANDRA-1403:
-------------------------------------
Attachment: v0-0001-fix-max-id-after-adding-a-column-family.txt
> 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.