cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sylvain Lebresne (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-9328) WriteTimeoutException thrown when LWT concurrency > 1, despite the query duration taking MUCH less than cas_contention_timeout_in_ms
Date Fri, 08 May 2015 18:18:02 GMT

    [ https://issues.apache.org/jira/browse/CASSANDRA-9328?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14535151#comment-14535151
] 

Sylvain Lebresne commented on CASSANDRA-9328:
---------------------------------------------

bq.  it seems that some updates that throw WTE really succeed

A WTE means that update may or may not be applied, so yes, the update may have succeeded if
you get a WTE.

> 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, 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)

Mime
View raw message