Ahh forgot to mention we have RF=2, sorry!
LWT requires RF >= 3 otherwise we can not tolerate losing a node (because
of LOCAL_QUORUM is working in the background which you can not really
change AFAIK...)
Or am I wrong?
Plus in a highly concurrent setup writing the same PK this optimistic
You can do this with conditional (CAS) updates - update ... set c=y if c=x
Requires serial writes and serial reads, so a bit more expensive, but allows
TTL.
> On Mar 6, 2021, at 8:03 AM, Attila Wind wrote:
>
>
> Hi guys,
>
> We do use Counter tables a lot because in our app we have
Hi guys,
We do use Counter tables a lot because in our app we have several things
to count (business logic)
More time we work with Cassandra we keep hearing more and more: "you
should not use counter tables because ."
Yes, we also feel here and there the trade off is too much
Thanks Bowen,
* "How do you split?"
challenging to answer short, but let me try: physical host has cores
from idx 0 - 11 (6 physical and 6 virtual in pairs - they are in
pairs as 0,6 belongs together, then 1,7 and then 2,8 and so on)
What we do is that in the virt-install command we
Hi Attila,
Addressing your data modelling issue is definitely important, and this
alone may be enough to solve all the issues you have with Cassandra.
* "Since these are VMs, is there any chance they are competing for
resources on the same physical host?"
We are splitting the physical
Hi Erick,
Please allow me to disagree on this. A node dropping reads and writes
doesn't always mean the disk is the bottleneck. I have seen the same
behaviour when a node had excessive STW GCs and a lots of timeouts, and
I have also seen writes get dropped because the size of the mutation
