Hi,
We want to throttle maximum queries on any keyspace for clients connecting
via CQL native transport. This option is available for clients connecting
via thrift by property of request_scheduler in cassandra.yaml.
Is there some option available for clients connecting via CQL native
transport.
Hi,
Thank you for the reply.
I've measured LWT throughput in 4.0.
I used the cassandra-stress tool to insert rows with LWT for 3 minutes on
i3.xlarge and i3.4xlarge
For 3.11, I modified the tool to support LWT.
Before each measurement, I cleaned up all Cassandra data.
The throughput in 4.0 is 5
Could also be the app not detecting the host is down and it keeps trying to use
it as a coordinator
--
Jeff Jirsa
> On Nov 27, 2018, at 6:33 PM, Ben Slater wrote:
>
> In what way does the cluster become unstable (ie more specifically what are
> the symptoms)? My first thought would be the
In what way does the cluster become unstable (ie more specifically what are
the symptoms)? My first thought would be the loss of the node causing the
other nodes to become overloaded but that doesn’t seem to fit with your
point 2.
Cheers
Ben
---
*Ben Slater*
*Chief Product Officer*
Hello all,
Setup:
18 Cassandra node cluster. Cassandra version 2.2.8
Amazon C3.2x large machines.
Replication factor of 3 (in 3 different AZs).
Read and Write using Quorum.
Use case:
1. Short lived data with heavy updates (I know we are abusing Cassandra
here) with gc grace period of 15
Hello,
I am trying to copy the content of a materialized view to a CSV using the
cqlsh COPY command (doc here :
https://docs.datastax.com/en/cql/3.3/cql/cql_reference/cqlshCopy.html).
When I use the command on a regular table It works perfectly, but it is not
working when I am doing it on a
