[
https://issues.apache.org/jira/browse/CASSANDRA-9328?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14534412#comment-14534412
]
Sylvain Lebresne commented on CASSANDRA-9328:
---------------------------------------------
This is unfortunately something known (and for which, to the best of my
knowledge we have no easy fix (CASSANDRA-6246 might well fix it but that's not
easy)). There is cases where under contention the coordinator loses track of
whether the value it submitted to Paxos might be applied or not (see
CASSANDRA-6013). At which point we can't do anything else that answering "sorry
I don't know". And since a {{WriteTimeoutException}} already means "I don't
know", we throw it in that case too, even though it's not a proper timeout
per-se. The point being, you should handle it as if it was a timeout.
> WriteTimeoutException thrown when LWT concurrency > 1, despite the query
> duration taking MUCH less than cas_contention_timeout_in_ms
> ------------------------------------------------------------------------------------------------------------------------------------
>
> Key: CASSANDRA-9328
> URL: https://issues.apache.org/jira/browse/CASSANDRA-9328
> Project: Cassandra
> Issue Type: Bug
> Components: Core
> Reporter: Aaron Whiteside
> Assignee: Benjamin Lerer
> Priority: Critical
> Fix For: 2.1.x
>
> Attachments: CassandraLWTTest.java
>
>
> WriteTimeoutException thrown when LWT concurrency > 1, despite the query
> duration taking MUCH less than cas_contention_timeout_in_ms.
> Unit test attached, run against a 3 node cluster running 2.1.5.
> If you reduce the threadCount to 1, you never see a WriteTimeoutException. If
> the WTE is due to not being able to communicate with other nodes, why does
> the concurrency >1 cause inter-node communication to fail?
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
