r be
> available for all keys. So long as there are still 3 "natural endpoints" for
> each key.
>
> Hope that helps.
>
> Aaron
>
> On 15/01/2011, at 8:52 AM, Mark Moseley wrote:
>
>>> Perhaps the better question would be, if I have a two node cluster and
&g
> Perhaps the better question would be, if I have a two node cluster and
> I want to be able to lose one box completely and replace it (without
> losing the cluster), what settings would I need? Or is that an
> impossible scenario? In production, I'd imagine a 3 node cluster being
> the minimum but
On Thu, Jan 13, 2011 at 2:32 PM, Mark Moseley wrote:
> On Thu, Jan 13, 2011 at 1:08 PM, Gary Dusbabek wrote:
>> It is impossible to properly bootstrap a new node into a system where
>> there are not enough nodes to satisfy the replication factor. The
>> cluster as it stand
On Thu, Jan 13, 2011 at 1:08 PM, Gary Dusbabek wrote:
> It is impossible to properly bootstrap a new node into a system where
> there are not enough nodes to satisfy the replication factor. The
> cluster as it stands doesn't contain all the data you are asking it to
> replicate on the new node.
I'm just starting to play with Cassandra, so this is almost certainly
a conceptual problem on my part, so apologies in advance. I was
testing out how I'd do things like bring up new nodes. I've got a
simple 2-node cluster with my only keyspace having
replication_factor=2. This is on 32-bit Debian S
