> And about range scan - as far as I understand, range scan could be done only
> with Order Preserving Partitioner, but not with Random Partitioner.
Range scan can be used with any partitioner.
If you use it with the RP the order of the rows will be ranged.
Cheers
-
Aaron Morto
Oh, I finally understand. As I read records one by one they aren't
necessarily read from a single node, so if I got 965 records out of 1000,
some of them could be read from other nodes which have all of 1000 records.
And about range scan - as far as I understand, range scan could be done
only with
Are you using a multi get or a range slice ?
Read Repair does not run for range slice queries.
Cheers
-
Aaron Morton
Freelance Cassandra Consultant
New Zealand
@aaronmorton
http://www.thelastpickle.com
On 15/05/2013, at 6:51 PM, Sergey Naumov wrote:
>> see that RR works, bu
see that RR works, but sometimes number of records have been read degrades.
RR is enabled on a random 10% of requests, see the read_repair_chance
setting for the CF.
OK, but I forgot to mention the main thing - each node in my config is a
standalone datacenter and distribution is DC1:1, DC2:1, DC
> see that RR works, but sometimes number of records have been read degrades.
RR is enabled on a random 10% of requests, see the read_repair_chance setting
for the CF.
> If so, then the question is: how to perform local reads to examine content
> of specific node?
You can check which nodes ar
Hello.
I'am playing with demo cassandra cluster and decided to test read repair +
hinted handoff.
One node of a cluster was put down deliberately, and on the other nodes I
inserted some records (say 1000). HH is off on all nodes.
Then I turned on the node, connected to it with cql (locally, so to
