[
https://issues.apache.org/jira/browse/CASSANDRA-9328?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14981230#comment-14981230
]
Aaron Whiteside commented on CASSANDRA-9328:
--------------------------------------------
Personally I think this is acceptable. As you will retry the CAS operation and
it will fail again (already applied, or someone else won).
The behavior should be correct under ideal conditions, currently it's
non-deterministic under ideal conditions.
> 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
> Reporter: Aaron Whiteside
> Priority: Critical
> Fix For: 2.1.x
>
> Attachments: CassandraLWTTest.java, CassandraLWTTest2.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)
