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] [Resolved] (CASSANDRA-10423) Paxos/LWT failures when moving node
Date Wed, 23 Dec 2015 08:29:46 GMT

     [ https://issues.apache.org/jira/browse/CASSANDRA-10423?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Sylvain Lebresne resolved CASSANDRA-10423.
------------------------------------------
       Resolution: Duplicate
    Fix Version/s:     (was: 2.1.x)

This _is_ almost surely due to CASSANDRA-10887 so closing as duplicate.

> Paxos/LWT failures when moving node
> -----------------------------------
>
>                 Key: CASSANDRA-10423
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-10423
>             Project: Cassandra
>          Issue Type: Bug
>         Environment: Cassandra version: 2.0.14
> Java-driver version: 2.0.11
>            Reporter: Roger Schildmeijer
>
> While moving a node (nodetool move <newtoken>) we noticed that lwt started failing
for some (~50%) requests. The java-driver (version 2.0.11) returned com.datastax.driver.core.exceptions.WriteTimeoutException:
Cassandra timeout during write query at consistency SERIAL (7 replica were required but only
0 acknowledged the write). The cluster was not under heavy load.
> I noticed that the failed lwt requests all took just above 1s. That information and the
WriteTimeoutException could indicate that this happens:
> https://github.com/apache/cassandra/blob/cassandra-2.0.14/src/java/org/apache/cassandra/service/StorageProxy.java#L268
> I can't explain why though. Why would there be more cas contention just because a node
is moving?



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message