[CASSANDRA-6558] Failure Detector takes 4-5x longer than it used to

• Type: Bug
• Status: Resolved
• Priority: Low
• Resolution: Duplicate
• Labels: datastax_qa
• Severity: Low
• Since Version: 2.0.3
• Assignee: Unassigned
• Reporter: Joaquin Casares
• Created: 07/Jan/14 19:24
• Updated: 16/Apr/19 09:31
• Resolved: 08/Jan/14 15:27

Description

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.

Issue Links

• duplicates: CASSANDRA-4375 FD incorrectly using RPC timeout to ignore gossip heartbeats