cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "sankalp kohli (JIRA)" <>
Subject [jira] [Commented] (CASSANDRA-10423) Paxos/LWT failures when moving node
Date Thu, 17 Dec 2015 00:09:46 GMT


sankalp kohli commented on CASSANDRA-10423:

[~slebresne] Why will there be more contention when there are more participants? Contention
depends upon if you have more clients which are updating the same CQL partitions. I don't
see how this should be affected. 

> Paxos/LWT failures when moving node
> -----------------------------------
>                 Key: CASSANDRA-10423
>                 URL:
>             Project: Cassandra
>          Issue Type: Bug
>         Environment: Cassandra version: 2.0.14
> Java-driver version: 2.0.11
>            Reporter: Roger Schildmeijer
>             Fix For: 2.1.x
> 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:
> 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

View raw message