Oh, I see it was clock drift in this case. Glad you found that out. Sean Durity
From: Durity, Sean R <sean_r_dur...@homedepot.com> 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 interesting question for a prepared statement where you are not binding all the variables. The driver or framework might be doing something you don’t expect. Sean Durity From: Sebastian Estevez <sebastian.este...@datastax.com<mailto:sebastian.este...@datastax.com>> Sent: Monday, March 23, 2020 9:02 PM To: user@cassandra.apache.org<mailto: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 it's common enough that I thought I would mention it. Hope you get to the bottom of it! All the best, Sebastián Estévez On Mon, Mar 23, 2020 at 8:50 PM Jeff Jirsa <jji...@gmail.com<mailto:jji...@gmail.com>> wrote: 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 (but unlikely) that you can have a really broken data file that simulates a deletion marker. You may be able to find this with sstable2json (older versions) or sstabledump (3.0+) sstabledump your data files that have the key (nodetool getendpoints, nodetool getsstables, sstabledump), look for something unusual. On Mon, Mar 23, 2020 at 4:00 PM Oliver Herrmann <o.herrmann...@gmail.com<mailto:o.herrmann...@gmail.com>> wrote: 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 consistency all) the row does not exist. When using the prepared statements we do not bind values to all placeholder for data columns but I think this should not be a problem, right? I checked system.log and debug.log for any hints but nothing is written into these log files. It's only happening in one specific cluster. When running the same software in other clusters everything is working fine. We are using Cassanda server version 3.11.1 and datastax cpp driver 2.13.0. Any idea how to analyze/fix this problem? Regards Oliver ________________________________ The information in this Internet Email is confidential and may be legally privileged. It is intended solely for the addressee. Access to this Email by anyone else is unauthorized. If you are not the intended recipient, any disclosure, copying, distribution or any action taken or omitted to be taken in reliance on it, is prohibited and may be unlawful. When addressed to our clients any opinions or advice contained in this Email are subject to the terms and conditions expressed in any applicable governing The Home Depot terms of business or client engagement letter. The Home Depot disclaims all responsibility and liability for the accuracy and content of this attachment and for any damages or losses arising from any inaccuracies, errors, viruses, e.g., worms, trojan horses, etc., or other items of a destructive nature, which may be contained in this attachment and shall not be liable for direct, indirect, consequential or special damages in connection with this e-mail message or its attachment. ________________________________ The information in this Internet Email is confidential and may be legally privileged. It is intended solely for the addressee. Access to this Email by anyone else is unauthorized. If you are not the intended recipient, any disclosure, copying, distribution or any action taken or omitted to be taken in reliance on it, is prohibited and may be unlawful. When addressed to our clients any opinions or advice contained in this Email are subject to the terms and conditions expressed in any applicable governing The Home Depot terms of business or client engagement letter. The Home Depot disclaims all responsibility and liability for the accuracy and content of this attachment and for any damages or losses arising from any inaccuracies, errors, viruses, e.g., worms, trojan horses, etc., or other items of a destructive nature, which may be contained in this attachment and shall not be liable for direct, indirect, consequential or special damages in connection with this e-mail message or its attachment.
