You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@cassandra.apache.org by "Jeff Jirsa (JIRA)" <ji...@apache.org> on 2017/12/14 04:27:00 UTC

[jira] [Resolved] (CASSANDRA-9939) CASSANDRA-8819 Same Bug

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

Jeff Jirsa resolved CASSANDRA-9939.
-----------------------------------
    Resolution: Duplicate

Hi there,

Grooming old tickets, I'm closing this because 8819 was marked as a duplicate of CASSANDRA-8058, and also because this branch (cassandra-2.0) is end-of-life.

If you believe this bug still impacts live branches, and that it's not fixed by any other JIRA issues, please reopen.



> CASSANDRA-8819 Same Bug
> -----------------------
>
>                 Key: CASSANDRA-9939
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-9939
>             Project: Cassandra
>          Issue Type: Bug
>            Reporter: Tom Lewis
>
> CASSANDRA-8819 was not actually included in the 2.0.13 release per release notes and the problem still exist. Moving a token generates errors still. 
> com.datastax.driver.core.exceptions.WriteTimeoutException: Cassandra timeout during write query at consistency LOCAL_QUORUM (3 replica were required but only 2 acknowledged the write)"



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@cassandra.apache.org
For additional commands, e-mail: commits-help@cassandra.apache.org