Hey Kyle,
What version of Cassandra are you running?
Can you share the full (anonymized) schema, including keyspace and table
definitions?
The trace behavior you’re seeing here might be caused by read speculation:
https://cassandra.apache.org/doc/5.0/cassandra/developing/cql/ddl.html#spec_retry
Hey Tibor - this was recently brought up in ASF Slack, fix is in review:
CASSANDRA-19902
Hey Bowen,
Are you able to reproduce the issue without running com.datastax.oss.cdc.agent?
I don't see any glaringly obvious bugs there indicated by the thread dump, but
it would be useful to rule that out, particularly because it runs as an agent
and manages new instances of C*-defined classes
Here’s the best post I’m aware of:
https://jolynch.github.io/pdf/cassandra-availability-virtual.pdf
> On Oct 7, 2024, at 17:30, Long Pan wrote:
>
>
> Hi Cassandra Community,
>
> I’m currently exploring the use of single vnode (single token) per node in
> large-scale Cassandra deployments. I
The user list is a more appropriate place for this kind of question.
Here’s the default reference.conf configuration file:
https://github.com/apache/cassandra-java-driver/blob/4.x/core/src/main/resources/reference.conf
Docs on configuration here:
https://github.com/apache/cassandra-java-driver/
Not to derail from the original conversation too far, but wanted to agree that
maximum connection establishment time on native transport would be useful. That
would provide a maximum duration before an updated client keystore is used for
connections, which can be used to safely roll out client k
> if the replication factor is 3 it just picks the other two nodes following
> the ring clockwise.
The coordinator for a given mutation is not necessarily a replica (depending on
whether token-aware routing is used by the client) so it may have to forward to
RF remote nodes, then wait for the r
40ms is definitely higher than expected. Have you run your queries with TRACING enabled to see where the latency is coming from?https://docs.datastax.com/en/cql-oss/3.3/cql/cql_reference/cqlshTracing.html40ms is also a fairly specific duration: https://eklitzke.org/the-caveats-of-tcp-nodelay> On Li
Hey Mitch,
The security upgrade schedule that your colleague is working on may well be
relevant. Is your entire cluster on 3.11.6 or are the failing hosts possibly on
a newer version?
Abe
> On Feb 26, 2023, at 10:38, Mitch Gitman wrote:
>
>
> We're running Cassandra 3.11.6 on AWS EC2 insta
