You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Matthew F. Dennis (JIRA)" <ji...@apache.org> on 2011/01/21 22:17:44 UTC

[jira] Assigned: (CASSANDRA-2026) creating/dropping keyspaces does not work reliably

     [ https://issues.apache.org/jira/browse/CASSANDRA-2026?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Matthew F. Dennis reassigned CASSANDRA-2026:
--------------------------------------------

    Assignee: Gary Dusbabek

> creating/dropping keyspaces does not work reliably
> --------------------------------------------------
>
>                 Key: CASSANDRA-2026
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-2026
>             Project: Cassandra
>          Issue Type: Bug
>    Affects Versions: 0.7.0
>         Environment: observed on EC2 and real HW
>            Reporter: Matthew F. Dennis
>            Assignee: Gary Dusbabek
>            Priority: Blocker
>
> Creating and/or dropping keyspaces on more than just a few nodes does not reliably work (observed multiple times on 5, 15 and 40 node clusters. never observed on single node clusters)
> Right after a cluster is booted, importing a schema from yaml works reliably.
> However, creating keyspaces (same for dropping keyspaces) via the CLI, either with -f or by pasting into the window usually does not work (though sometimes it does).  In particular, only some nodes show the new changes while others do not.  ; 
> Often the changes are only reflected on the node where they were made, but not on any other node.  Most of the time some small subset of the nodes get the changes, but the majority do not.
> Sometimes it takes several attempts to expose the problem.  Once it happens the first time though, it continues to happen reliably on every change after the problem is first observed.
> In most cases all changes were executed from the same seed node.  It also happens when executed from non-seed nodes though.

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