You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Sylvain Lebresne (JIRA)" <ji...@apache.org> on 2014/01/08 16:27:58 UTC
[jira] [Resolved] (CASSANDRA-6558) Failure Detector takes 4-5x
longer than it used to
[ https://issues.apache.org/jira/browse/CASSANDRA-6558?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Sylvain Lebresne resolved CASSANDRA-6558.
-----------------------------------------
Resolution: Duplicate
> Failure Detector takes 4-5x longer than it used to
> --------------------------------------------------
>
> Key: CASSANDRA-6558
> URL: https://issues.apache.org/jira/browse/CASSANDRA-6558
> Project: Cassandra
> Issue Type: Bug
> Reporter: Joaquin Casares
> Priority: Minor
> Labels: datastax_qa
>
> The Failure Detector appears to also be used by the java-driver (https://datastax-oss.atlassian.net/browse/JAVA-246) in determining if nodes are down or not. Because of the recent increase in time that it takes for Cassandra to noticed downed nodes, tests within the java-driver integration suite are currently failing.
> This should only impact driver usage minimally since it also relies on failed requests to find out if a node is down, but fixing the issue means we get the tests back online and the Failure Detector working as it previously had been.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)