using https://www.zoho.com/mail/
Forwarded message
From: onmstester onmstester
To: "user"
Date: Sat, 14 Nov 2020 08:24:14 +0330
Subject: Re: local read from coordinator
Forwarded message
Thank you Jeff,
I disabled dynami
to:alex...@gmail.com>
To: "user"<mailto:user@cassandra.apache.org>
Date: Wed, 11 Nov 2020 11:28:56 +0330
Subject: Re: local read from coordinator
Forwarded message
token-aware policy doesn't work for token range queries (at least in the Java
driv
I appreciate the update to my understanding of the read path! Thanks, Jeff.
Sean Durity
From: Jeff Jirsa
Sent: Wednesday, November 11, 2020 10:33 AM
To: cassandra
Subject: [EXTERNAL] Re: local read from coordinator
What you describe is true for writes but not reads.
The read only gets sent
only with no other connections to
>> other nodes!
>>
>> Sent using Zoho Mail <https://www.zoho.com/mail/>
>>
>>
>>
>> ======== Forwarded message
>> From: Alex Ott
>> To: "user"
>> Date: Wed, 11 Nov 2020 11:28:56
inator)? And the first one that is able to respond wins (for
> LOCAL_ONE). That was my understanding.
>
>
>
> Sean Durity
>
>
>
> *From:* Jeff Jirsa
> *Sent:* Wednesday, November 11, 2020 9:24 AM
> *To:* user@cassandra.apache.org
> *Subject:* [EXTERNAL] Re: local re
: [EXTERNAL] Re: local read from coordinator
This isn’t necessarily true and cassandra has no coordinator-only consistency
level to force this behavior
(The snitch is going to pick the best option for local_one reads and any
compactions or latency deviations from load will make it likely that
===
>> From: Alex Ott
>> To: "user"
>> Date: Wed, 11 Nov 2020 11:28:56 +0330
>> Subject: Re: local read from coordinator
>> Forwarded message
>>
>> token-aware policy doesn't work for token range queries (at
dinator only with no other connections to
> other nodes!
>
> Sent using Zoho Mail <https://www.zoho.com/mail/>
>
>
>
> Forwarded message
> From: Alex Ott
> To: "user"
> Date: Wed, 11 Nov 2020 11:28:56 +0330
> Subject
user"
Date: Wed, 11 Nov 2020 11:28:56 +0330
Subject: Re: local read from coordinator
Forwarded message
token-aware policy doesn't work for token range queries (at least in the Java
driver 3.x). You need to force the driver to do the reading using a specific
to
token-aware policy doesn't work for token range queries (at least in the
Java driver 3.x). You need to force the driver to do the reading using a
specific token as a routing key. Here is Java implementation of the token
range scanning algorithm that Spark uses:
https://github.com/alexott/cassandr
Yes, use a token-aware policy so the driver will pick a coordinator where
the token (partition) exists. Cheers!
Hi,
I'm going to read all the data in the cluster as fast as possible, i'm aware
that spark could do such things out of the box but just wanted to do it at low
level to see how fast it could be. So:
1. retrieved partition keys on each node using nodetool ring token ranges and
getting distinct p
12 matches
Mail list logo
