Thanks Ryan,
I am using the java driver with token aware policy(dcawarepolicy) we have
all nodes on one DC. model for now is
partition_key, value
I think by hot partition you mean insertions to the same partition key ? we
have RF:3 and CL: 1 (will re run with local quorum as that is what we will
Totally depends on the load balancing policy of your driver, your data model,
consistently level and you’re replication factor. The default token aware
policy for the DataStax java driver up to 2.1.4 and 2.0.9 would largely behave
this way if you combined it with a hot partition, and all other l
Nope not using thrift
On 22-Apr-2015 7:24 pm, "Benedict Elliott Smith"
wrote:
> If you're connecting via thrift, all your traffic is most likely being
> routed to just one node, which then communicates with the other nodes for
> you.
>
> On Wed, Apr 22, 2015 at 6:11 AM, Anishek Agarwal
> wrote:
If you're connecting via thrift, all your traffic is most likely being
routed to just one node, which then communicates with the other nodes for
you.
On Wed, Apr 22, 2015 at 6:11 AM, Anishek Agarwal wrote:
> Forwarding it here, someone with Cassandra internals knowledge can help may
> be
>
>
