cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Joaquin Casares (JIRA)" <>
Subject [jira] [Commented] (CASSANDRA-6558) Failure Detector takes 4-5x longer than it used to
Date Thu, 09 Jan 2014 00:30:50 GMT


Joaquin Casares commented on CASSANDRA-6558:

[~slebresne] I gave that whirl on a few random lines of code and they started spitting errors.
I remember while coding, I ended up going with forceStop() since it allowed for faster shutdown
times, especially when trying to catch/force issues. If I were to switch all of them to stops()
it wouldn't hit the same expected cases.

Let's see if CASSANDRA-4375 fixes this, if not we can revisit and see if we can get a disable
FD command/switch/config.

> Failure Detector takes 4-5x longer than it used to
> --------------------------------------------------
>                 Key: CASSANDRA-6558
>                 URL:
>             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 (
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