On Thu, Aug 14, 2014 at 9:24 AM, Rene Kochen
wrote:
> I am using 1.0.11, so I only have read_repair_chance.
>
I'm sure this goes without saying, but you should upgrade to the head of
1.2.x (probably via 1.1.x) ASAP. I would not want to operate 1.0.11 in
production in 2014.
=Rob
I am using 1.0.11, so I only have read_repair_chance.
However, after testing I see that read_repair_chance does work for
local_quorum.
Based on this site:
http://www.datastax.com/documentation/cassandra/2.0/cassandra/architecture/architectureClientRequestsRead_c.html
I got the impression that rea
dclocal_read_repair_chance option on the table is your friend
http://www.datastax.com/documentation/cassandra/2.0/cassandra/reference/referenceTableAttributes.html?scroll=reference_ds_zyq_zmz_1k__dclocal_read_repair_chance
On Thu, Aug 14, 2014 at 4:53 PM, Rene Kochen
wrote:
> Hi all,
>
> I hav
Hi all,
I have a question about communication between two data-centers, both with
replication-factor three.
If I read data using local_quorum from datacenter1, I see that digest
requests are sent to datacenter2. This is for read-repair I guess. How can
I prevent this from happening? Setting read_
