cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Brandon Williams (JIRA)" <>
Subject [jira] [Commented] (CASSANDRA-6558) Failure Detector takes 4-5x longer than it used to
Date Tue, 07 Jan 2014 21:26:50 GMT


Brandon Williams commented on CASSANDRA-6558:

We could add a private method to the FD to basically disable CASSANDRA-6385 that you could
call.  That said, using the FD on the client side smells funny to me.

> Failure Detector takes 4-5x longer than it used to
> --------------------------------------------------
>                 Key: CASSANDRA-6558
>                 URL:
>             Project: Cassandra
>          Issue Type: Bug
>            Reporter: Joaquin Casares
>              Labels: datastax_qa
> The Failure Detector appears to also be used by the java-driver (
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

View raw message