[jira] [Updated] (CASSANDRA-10423) Paxos/LWT failures when moving node
[ https://issues.apache.org/jira/browse/CASSANDRA-10423?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jeremy Hanna updated CASSANDRA-10423: - Labels: LWT (was: ) > 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 >Priority: Major > Labels: LWT > > While moving a node (nodetool move ) 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 (v7.6.3#76005) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-10423) Paxos/LWT failures when moving node
[ https://issues.apache.org/jira/browse/CASSANDRA-10423?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksey Yeschenko updated CASSANDRA-10423: -- Assignee: (was: Ryan McGuire) > 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 > Fix For: 2.1.x > > > While moving a node (nodetool move ) 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)
[jira] [Updated] (CASSANDRA-10423) Paxos/LWT failures when moving node
[ https://issues.apache.org/jira/browse/CASSANDRA-10423?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksey Yeschenko updated CASSANDRA-10423: -- Fix Version/s: 2.1.x > 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 > Fix For: 2.1.x > > > While moving a node (nodetool move ) 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)
[jira] [Updated] (CASSANDRA-10423) Paxos/LWT failures when moving node
[ https://issues.apache.org/jira/browse/CASSANDRA-10423?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Roger Schildmeijer updated CASSANDRA-10423: --- Description: While moving a node (nodetool move ) 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? was:While moving a node (nodetool move ) 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. > Paxos/LWT failures when moving node > --- > > Key: CASSANDRA-10423 > URL: https://issues.apache.org/jira/browse/CASSANDRA-10423 > Project: Cassandra > Issue Type: Bug > Components: Core > Environment: Cassandra version: 2.0.14 > Java-driver version: 2.0.11 >Reporter: Roger Schildmeijer > > While moving a node (nodetool move ) 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)
