ssage ---
From: Durity, Sean R;
Received: Tue Mar 24 2020 14:17:10 GMT-0400 (Eastern Daylight Time)
To: user@cassandra.apache.org;
Subject: RE: Table not updating
I’m wondering about nulls. They are written as tombstones. So, it is an
interesting question for a prepared statement where you are not bi
Oh, I see it was clock drift in this case. Glad you found that out.
Sean Durity
From: Durity, Sean R
Sent: Tuesday, March 24, 2020 2:10 PM
To: user@cassandra.apache.org
Subject: [EXTERNAL] RE: Table not updating
I’m wondering about nulls. They are written as tombstones. So, it is an
, 2020 9:02 PM
To: user@cassandra.apache.org
Subject: [EXTERNAL] Re: Table not updating
I have seen cases where folks thought they were writing successfully to the
database but were really hitting timeouts due to an unhandled future in their
loading program. This may very well not be your issue but
Hi Erick, thank you for the hint with NTP. For some reasons ntpd was not
running on a few nodes and time was off by 2 Minutes. After restarting ntpd
and adjusting the time everything is working as expected. Thank you very
much. Al the best.
Am Di., 24. März 2020 um 01:47 Uhr schrieb Erick Ramirez
I have seen cases where folks thought they were writing successfully to the
database but were really hitting timeouts due to an unhandled future in
their loading program. This may very well not be your issue but it's common
enough that I thought I would mention it.
Hope you get to the bottom of it
You need to see what's in that place, it could be:
1) Delete in the future (viewable with SELECT WRITETIME(column) ...). This
could be clock skew or using the wrong resolution timestamps (millis vs
micros)
2) Some form of corruption if you dont have compression + crc check chance.
It's possible (b
Oliver, by chance are you also doing a TTL on the data? Or maybe you've
already issued a DELETE that has a future timestamp?
The only other way I can see this happening is when the node's clocks
are skewed. Have you checked whether NTP hasn't drifted by a massive
amount? Cheers!
GOT QUESTIONS? Ap
Hello,
we are facing a strange issue in one of our Cassandra clusters.
We are using prepared statements to update a table with consistency local
quorum. When updating some tables it happes very often that data values are
not written to the database. When verifying the table using cqlsh (with
consi
