Re: strange behavior of counter tables after losing a node

Thanks Elliott, yepp! This is exactly what we also figured out as a next step. Upgrade our TEST env to that so we can re-evaluate the test we did. Makes 100% sense Attila Wind http://www.linkedin.com/in/attilaw Mobile: +49 176 43556932 27.01.2021 10:18

Re: strange behavior of counter tables after losing a node

To start with, maybe update to beta4. There's an absolute massive list of fixes since alpha4. I don't think the alphas are expected to be in a usable/low-bug state necessarily, where beta4 is approaching RC status. On Tue, Jan 26, 2021, 10:44 PM Attila Wind wrote: > Hey All, > > I'm coming

Re: strange behavior of counter tables after losing a node

Hey All, I'm coming back on my own question (see below) as this has happened again to us 2 days later so we took the time to further analyse this issue. I'd like to share our experiences and the workaround which we figured out too. So to just quickly sum up the most important details again:

strange behavior of counter tables after losing a node

Hey guys, Yesterday we had an outage after we have lost a node and we saw such a behavior we can not explain. Our data schema has both: counter and norma tables. And we have replicationFactor = 2 and consistency level LOCAL_ONE (explicitly set) What we saw: After a node went down the