Re: Query timed out after PT1M

Ouch, counters. Counters in Cassandra have pretty bad performance comparing to everything else in Cassandra or counters (and their equivalent, such as integer types) in other mainstream databases, and they often are inaccurate too. I personally would recommend against the use of counters in C

Re: Query timed out after PT1M

Interestingly, I just tried creating two CqlSession objects and when I use both instead of a single CqlSession for all queries, the 'No Node available to execute query' no longer happens.  In other words, if I use a different CqlSession for updating the doc.seq table, it works.  If that session

Re: Query timed out after PT1M

Thank you Bowen - I wasn't familiar with PT1M. I'm doing the following: update doc.seq set doccount=doccount+? where id=? Which runs OK. Immediately following the update, I do: select doccount from doc.seq where id=? It is the above statement that is throwing the error under heavy load. The sele

Re: Query timed out after PT1M

The error message is clear, it was a DriverTimeoutException, and it was because the query timed out after one minute. /Note: "PT1M" means a period of one minute, see //https://en.wikipedia.org/wiki/ISO_8601#Durations / If you need help from u