[
https://issues.apache.org/jira/browse/CASSANDRA-6558?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13866866#comment-13866866
]
Joaquin Casares commented on CASSANDRA-6558:
--------------------------------------------
heh, I figured to wait until CASSANDRA-4375 was released to see how I could use
it since it wouldn't matter for this java-driver release.
I've read it now. Thanks for the clarification. :)
> 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)
