nhaddad.com]
> *Sent:* jeudi 31 mars 2016 17:48
>
> *To:* user@cassandra.apache.org
> *Subject:* Re: How many nodes do we require
>
>
>
> Losing a write is very different from having a fragile cluster. A fragile
> cluster implies that whole thing will fall apart,
You’re right. I meant about data integrity, I understand it’s not everybody’s
priority!
--
Jacques-Henri Berthemet
From: Jonathan Haddad [mailto:j...@jonhaddad.com]
Sent: jeudi 31 mars 2016 17:48
To: user@cassandra.apache.org
Subject: Re: How many nodes do we require
Losing a write is very
if
> it was not yet replicated.
>
>
>
> *--*
>
> *Jacques-Henri Berthemet*
>
>
>
> *From:* Jonathan Haddad [mailto:j...@jonhaddad.com]
> *Sent:* vendredi 25 mars 2016 19:37
>
>
> *To:* user@cassandra.apache.org
> *Subject:* Re: How many nodes do we req
gt; Because if you lose a node you have chances to lose some data forever if
>> it was not yet replicated.
>>
>>
>>
>> *--*
>>
>> *Jacques-Henri Berthemet*
>>
>>
>>
>> *From:* Jonathan Haddad [mailto:j...@jonhaddad.com]
>> *Sent:* v
>
>
> *From:* Jonathan Haddad [mailto:j...@jonhaddad.com]
> *Sent:* vendredi 25 mars 2016 19:37
>
> *To:* user@cassandra.apache.org
> *Subject:* Re: How many nodes do we require
>
>
>
> Why would using CL-ONE make your cluster fragile? This isn't obvious to
> me. It's
Because if you lose a node you have chances to lose some data forever if it was
not yet replicated.
--
Jacques-Henri Berthemet
From: Jonathan Haddad [mailto:j...@jonhaddad.com]
Sent: vendredi 25 mars 2016 19:37
To: user@cassandra.apache.org
Subject: Re: How many nodes do we require
Why would
; Jacques-Henri Berthemet
>
>
> -Original Message-
> From: Rakesh Kumar [mailto:rakeshkumar46...@gmail.com]
> Sent: vendredi 25 mars 2016 18:14
> To: user@cassandra.apache.org
> Subject: Re: How many nodes do we require
>
> On Fri, Mar 25, 2016 at 11:45 AM, Jack Krupansky
&
Message-
From: Rakesh Kumar [mailto:rakeshkumar46...@gmail.com]
Sent: vendredi 25 mars 2016 18:14
To: user@cassandra.apache.org
Subject: Re: How many nodes do we require
On Fri, Mar 25, 2016 at 11:45 AM, Jack Krupansky
wrote:
> It depends on how much data you have. A single node can store a lot
On Fri, Mar 25, 2016 at 11:45 AM, Jack Krupansky
wrote:
> It depends on how much data you have. A single node can store a lot of data,
> but the more data you have the longer a repair or node replacement will
> take. How long can you tolerate for a full repair or node replacement?
At this time, f
It depends on how much data you have. A single node can store a lot of
data, but the more data you have the longer a repair or node replacement
will take. How long can you tolerate for a full repair or node replacement?
Generally, RF=3 is both sufficient and recommended.
-- Jack Krupansky
On Fri
We have two data centers. Our requirement is simple
Assuming that we have equal number of nodes in each DC we should be able to run
with the loss of one DC and loss of at most one node in the surviving DC. Can
this be achieved with 6 nodes (3 in each). Obviously for that all data must be
availa
11 matches
Mail list logo