incubator-cassandra-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Gary Dusbabek <gdusba...@gmail.com>
Subject Re: New keyspace loading creates 'master'
Date Fri, 11 Jun 2010 11:42:56 GMT
I've filed this as
https://issues.apache.org/jira/browse/CASSANDRA-1182.  I've created
steps to reproduce based on your email and placed them in the ticket
description.  Can you confirm that I've described things correctly?

Gary.

On Thu, Jun 10, 2010 at 17:16, Ronald Park <ronald.park@cbs.com> wrote:
> Hi,
>
> We've been fiddling around with a small Cassandra cluster, bringing nodes up
> and down, to get a feel for how things are replicated and how spinning up a
> new node works (before having to learn it live :).  We are using the trunk
> because we want to use the expiration feature.  Along with that comes the
> new keyspace api to load the 'schema'.
>
> What we found was that, if the node on which we originally installed the
> keyspace was down when a new node is added, the new node does not get the
> keyspace schema.  In some regards, it is now the 'master', at least in
> distributing the keyspace data.  Is this a known limitation?
>
> Thanks,
> Ron
>

Mime
View raw message