ndra.apache.org>>
Date: Wednesday, October 23, 2019 at 3:34 PM
To: "user@cassandra.apache.org<mailto:user@cassandra.apache.org>"
mailto:user@cassandra.apache.org>>
Subject: Re: Cassandra Rack - Datacenter Load Balancing relations
Message from External Sender
Hi Reid,
Than
nd I’m half asleep. I
> prefer simple until the workload motivates complex.
>
>
>
> R
>
>
>
>
>
> *From: *Sergio
> *Reply-To: *"user@cassandra.apache.org"
> *Date: *Thursday, October 24, 2019 at 12:06 PM
> *To: *"user@cassandra.apache.org&qu
at 3 in the morning and I’m half asleep. I prefer simple
until the workload motivates complex.
R
From: Sergio
Reply-To: "user@cassandra.apache.org"
Date: Thursday, October 24, 2019 at 12:06 PM
To: "user@cassandra.apache.org"
Subject: Re: Cassandra Rack - Datacenter Load
ate.
>
>
> R
>
>
>
> *From: *Sergio
> *Reply-To: *"user@cassandra.apache.org"
> *Date: *Wednesday, October 23, 2019 at 3:34 PM
> *To: *"user@cassandra.apache.org"
> *Subject: *Re: Cassandra Rack - Datacenter Load Balancing relations
>
>
>
&
er 23, 2019 at 12:50 PM
To: "user@cassandra.apache.org<mailto:user@cassandra.apache.org>"
mailto:user@cassandra.apache.org>>
Subject: Re: Cassandra Rack - Datacenter Load Balancing relations
Message from External Sender
Hi Reid,
Thanks for your reply. I really appreciate your explanation
>or wrong assumption? I am thinking that I will write a blog post about
>>>>> all
>>>>> my learnings so far, thank you very much for the replies Best, Sergio
>>>>>
>>>>>
>>>>> Il giorno mer 23 ott 2019 alle ore 10:57
oint of racks is to help you distribute
>>>>> the replicas, not further-replicate the replicas. Data centers are what
>>>>> do
>>>>> the latter. So for example, if you wanted to be able to ensure that you
>>>>> always had quorum i
rack in each DC. In your situation I think I’d
>>>> be more tempted to consider that. Then if an AZ went away, you could fail
>>>> over your traffic to the remaining DC and still be perfectly fine.
>>>>
>>>>
>>>>
>>>> For
kTopologyStrategy’ at:
>>>
>>> http://cassandra.apache.org/doc/latest/architecture/dynamo.html
>>>
>>>
>>>
>>> That should help you better understand how replicas distribute.
>>>
>>>
>>>
>>> As mentioned bef
ork traffic and
>> connection handling, you can’t isolate reads from writes. You can _
>> *mostly*_ insulate the write DC from the activity within the read DC,
>> and even that isn’t an absolute because of repairs. However, your mileage
>> may vary, so do what make
gio
> *Reply-To: *"user@cassandra.apache.org"
> *Date: *Wednesday, October 23, 2019 at 12:50 PM
> *To: *"user@cassandra.apache.org"
> *Subject: *Re: Cassandra Rack - Datacenter Load Balancing relations
>
>
>
> *Message from External Sender*
>
> Hi
: Sergio
Reply-To: "user@cassandra.apache.org"
Date: Wednesday, October 23, 2019 at 12:50 PM
To: "user@cassandra.apache.org"
Subject: Re: Cassandra Rack - Datacenter Load Balancing relations
Message from External Sender
Hi Reid,
Thanks for your reply. I really appreciate y
Hi Reid,
Thanks for your reply. I really appreciate your explanation.
We are in AWS and we are using right now 2 Availability Zone and not 3. We
found our cluster really unbalanced because the keyspace has a replication
factor = 3 and the number of racks is 2 with 2 datacenters.
We want the
Datacenters and racks are different concepts. While they don't have to be
associated with their historical meanings, the historical meanings probably
provide a helpful model for understanding what you want from them.
When companies own their own physical servers and have them housed somewhere,
Hello guys!
I was reading about
https://cassandra.apache.org/doc/latest/architecture/dynamo.html#networktopologystrategy
I would like to understand a concept related to the node load balancing.
I know that Jon recommends Vnodes = 4 but right now I found a cluster with
vnodes = 256 replication
15 matches
Mail list logo
