[
https://issues.apache.org/jira/browse/CASSANDRA-9328?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15101696#comment-15101696
]
James Howe edited comment on CASSANDRA-9328 at 1/15/16 12:46 PM:
-----------------------------------------------------------------
Am I understanding this correctly? If a SERIAL write throws a
WriteTimeoutException, I must then perform a SERIAL read to find out whether it
actually succeeded or not? Or is not that even guaranteed to work?
was (Author: jameshowe):
Am I understanding this correctly? If a SERIAL write throws a
WriteTimeoutException, I must then perform a SERIAL read to find out whether it
actually succeeded or not?
> 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: Coordination
> Reporter: Aaron Whiteside
> 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)
