Hi @Erick Ramirez, I was reading this answer from you: https://community.datastax.com/questions/5647/coordinator.html# about write consistency levels and the exceptions that drivers report. I was curious about this one in particular:
WriteTimeoutException: Cassandra timeout during SIMPLE write query at consistency LOCAL_QUORUM (2 replica were required but only 1 acknowledged the write)"
This simply means that there was a delay in ack from 1 replica, but does not necessarily mean that the write itself failed on that replica. If I understand it right, it's now up to the application on how to handle this error.
From what I've understood so far, there are multiple cases here:
- Writes were successful on both replicas, but one of the replica did not respond with ack in time, to the coordinator.
- The data was written successfully on one replica, but not on the other. But since the data was written to one of the replicas, eventually the other replica would also get the data. So even if the application did not act on this error, data would eventually be consistent on the 2 replicas, by means of hinted-handoffs (?) / read repairs.
Could you please let me know if my understanding is right? If not, please correct me :)
What will happen if a write timeout occurs, on the subsequent read request? My writes are EACH_QUORUM and reads are LOCAL_QUORUM