cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Brandon Williams (JIRA)" <>
Subject [jira] [Commented] (CASSANDRA-3533) TimeoutException when there is a firewall issue.
Date Tue, 31 Jul 2012 03:23:35 GMT


Brandon Williams commented on CASSANDRA-3533:

To answer my own question, the problem is that a coordinator can be completely isolated from
a given replica set and be forced to time out for any requests to it.

If we do poll via some kind of no-op message or something similar, it seems the main wrinkle
will be knowing how long to wait before giving up on a reply.  We could estimate from the
FD, except in cases where we have no data at all, which is most likely to be the common one.
> TimeoutException when there is a firewall issue.
> ------------------------------------------------
>                 Key: CASSANDRA-3533
>                 URL:
>             Project: Cassandra
>          Issue Type: Improvement
>          Components: Core
>            Reporter: Vijay
>            Assignee: Brandon Williams
>            Priority: Minor
>             Fix For: 1.2
>         Attachments: 3533.txt
> When one node in the cluster is not able to talk to the other DC/RAC due to firewall
or network related issue (StorageProxy calls fail), and the nodes are NOT marked down because
at least one node in the cluster can talk to the other DC/RAC, we get timeoutException instead
of throwing a unavailableException.
> The problem with this:
> 1) It is hard to monitor/identify these errors.
> 2) It is hard to diffrentiate from the client if the node being bad vs a bad query.
> 3) when this issue happens we have to wait for at-least the RPC timeout time to know
that the query wont succeed.
> Possible Solution: when marking a node down we might want to check if the node is actually
alive by trying to communicate to it? So we can be sure that the node is actually alive.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:!default.jspa
For more information on JIRA, see:


View raw message