Note that that writetimeout exception can be C*s way of telling you when
there is contention on a LWT (rather than actually timing out). See
https://issues.apache.org/jira/browse/CASSANDRA-9328
Cheers
Ben
On Sun, 22 Jul 2018 at 11:20 Goutham reddy
wrote:
> Hi,
> As it is a single partition
Hi,
As it is a single partition key, try to update the key with only partition
key instead of passing other columns. And try to set consistency level ONE.
Cheers,
Goutham.
On Fri, Jul 20, 2018 at 6:57 AM learner dba
wrote:
> Anybody has any ideas about this? This is happening in production and
Hi,
Consider overriding default java driver provided by spring boot if you are
using Datastax clusters with with any of the 3.X Datastax driver. I agree
to Patrick, always have one key space specified to one application in that
way you achieve domain driven applications and cause less overhead
Hello,
We are running Cassandra 2.1.14 in AWS, with c5.4xlarge machines
(initially these were m4.xlarge) for our cassandra servers and
m4.xlarge for our application servers. On one of our clusters having
problems we have 6 C* nodes and 6 AS nodes (two nodes for C*/AS in
each availability zone).
