Hi, DataStax Cassandra 4.14 is actually the driver's version. Almost the latest https://mvnrepository.com/artifact/com.datastax.oss/java-driver-core
It would be useful to know which version of Cassandra you are using, even if, it would be surprised it is actually the cause of your error. As it has been mentioned above the root cause is => A client-side timeout considering that the request is too slow, server did not respond in time. The reasons are legions: - The cluster can be busy (hot partitions) - You can query more and more data which taking more and more time (large partitions) - You have not designed your data model based on your queries, and, as a result, do cross-partition queries. - You perform full scans of your cluster with (stupid) ALLOW FILTERING. - You are using the IN clause (same as above) But, to be honest, my gut feeling is something that I keep seeing coming back => I bet you might have moved to the latest SPRING DATA CASSANDRA version. This thing keeps preparing everything like crazy as which leads to timeouts tend to pop up here and there. It is not easy to explain as if you prepare twice the same statement nothing happens it has been kept in the cache. Is there anything else at work? Is anybody having heard about the same issues lately? On Wed, Nov 9, 2022 at 4:10 PM Durity, Sean R via user < user@cassandra.apache.org> wrote: > From the subject, this looks like a client-side timeout (thrown by the > driver). I have seen situations where the client/driver timeout of 2 > seconds is a shorter timeout than on the server side (10 seconds). So, the > server doesn’t really note any problem. Unless this is a very remote client > and you suspect network-related latency, I would start by looking at the > query that generates the timeout and the schema of the table. Make sure > that you are querying WITHIN a partition and not ACROSS partitions. There > are plenty of other potential problems, but you would need to give us more > data to guide those discussions. > > > > Sean R. Durity > > > > *From:* Bowen Song via user <user@cassandra.apache.org> > *Sent:* Tuesday, November 8, 2022 1:53 PM > *To:* user@cassandra.apache.org > *Subject:* [EXTERNAL] Re: Query drivertimeout PT2S > > > > This is a mailing list for the Apache Cassandra, and that's not the same > as DataStax Enterprise Cassandra you are using. We may still be able to > help here if you could provide more details, such as the queries, table > schema, system stats (cpu, > > This is a mailing list for the Apache Cassandra, and that's not the same > as DataStax Enterprise Cassandra you are using. We may still be able to > help here if you could provide more details, such as the queries, table > schema, system stats (cpu, ram, disk io, network, and so on), logs, table > stats, etc., but if it's a DSE Cassandra specific issue, you may have > better luck contacting DataStax directly or posting it on the DataStax > Community [community.datastax.com] > <https://urldefense.com/v3/__https:/community.datastax.com/topics/82/cassandra.html__;!!M-nmYVHPHQ!JeQFduuBvu8AGLCMA3uqnA0pnlFvt5Iqg2uUP1aQQXjlHf7LRNqEotOSqIsxVc0j6sT7uh_U3G__LbiyoZ-2QrKTN0Q$> > . > > On 08/11/2022 14:58, Shagun Bakliwal wrote: > > Hi All, > > > > My application is frequently getting timeout errors since 2 weeks now. I'm > using datastax Cassandra 4.14 > > > > Can someone help me here? > > > > Thanks, > > Shagun > > > > INTERNAL USE > > -- Cedrick Lunven e. cedrick.lun...@datastax.com w. www.datastax.com
