> Therefore I was wondering if Cassandra already intelligently optimizes
> for HH-over-WAN (since this is common) or alternately if there's a way
> to enable HH for WAN replication?
When the coordinator is preparing to process the request, done nodes in a
foreign DC are treated like down nodes in
I re-read my last post and didn't think I had done a good job articulating.
Sorry! I'll try again...
Say I choose LOCAL_QUORUM with a Replication Factor of 3. Cassandra
stores three copies in my local datacenter. Therefore the cost
associated with "losing" one node is not very high locally, and I
Let me attempt to articulate my question a little better.
Say I choose LOCAL_QUORUM with a Replication Factor of 3. Cassandra
stores three copies in my local datacenter. Therefore the cost
associated with "losing" one node is not very high locally, and I
usually HH, and use read repair/nodetool re
On Tue, Jun 26, 2012 at 8:16 AM, Karthik N wrote:
> Since Cassandra optimizes and sends only one copy over the WAN, can I opt
> in only for HH for WAN replication and avoid HH for the local quorum?
> (since I know I have more copies)
>
>
>
I am not sure if I understand your question. In general I
Since Cassandra optimizes and sends only one copy over the WAN, can I opt
in only for HH for WAN replication and avoid HH for the local quorum?
(since I know I have more copies)
On Tuesday, June 26, 2012, Mohit Anchlia wrote:
>
> On Tue, Jun 26, 2012 at 7:52 AM, Karthik N
>
> > wrote:
>
>> My C
On Tue, Jun 26, 2012 at 7:52 AM, Karthik N wrote:
> My Cassandra ring spans two DCs. I use local quorum with replication
> factor=3. I do a write in DC1 with local quorum. Data gets written to
> multiple nodes in DC1. For the same write to propagate to DC2 only one
> copy is sent from the coordin
My Cassandra ring spans two DCs. I use local quorum with replication
factor=3. I do a write in DC1 with local quorum. Data gets written to
multiple nodes in DC1. For the same write to propagate to DC2 only one
copy is sent from the coordinator node in DC1 to a coordinator node in
DC2 for optimizing