https://issues.apache.org/jira/browse/CASSANDRA-9620 has something similar that was determined to be a driver error. I would start with looking at the driver version and also the RetryPolicy that is in effect for the Cluster. Secondly, I would look at whether a batch is really needed for the statements. Cassandra batches are for atomicity – not speed.
Staff Systems Engineer – Cassandra
#cassandra - for the latest news and updates
I want to understand how you are setting the write consistency level as LOCAL ONE. That is with every query you mentioning consistency level or you have set the spring cassandra config with provided consistency level.
The only possibility i see of such behavior is its getting overridden from some where.
On Thu, Apr 11, 2019 at 1:43 PM Jean Carlo <email@example.com> wrote:
I have a case where the developers are using spring data framework for Cassandra. We are writing batches setting consistency level at LOCAL_ONE but we got a timeout like this
Caused by: com.datastax.driver.core.exceptions.WriteTimeoutException: Cassandra timeout during BATCH_LOG write query at consistency TWO (2 replica were required but only 1 acknowledged the write)
Is it Cassandra that somehow writes to the system.batchlog using consistency TWO or is it spring data that makes some dirty things behind the scenes ?
(I want to believe it is the second one)
"The best way to predict the future is to invent it" Alan Kay
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.