[
https://issues.apache.org/jira/browse/GEODE-3948?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16341406#comment-16341406
]
Bruce Schuchardt commented on GEODE-3948:
-----------------------------------------
Testing with iptable manipulation shows that a client does not detect that the
server is not reachable, and the server does not detect that the client is not
there. The client's sotimeout setting on its socket works during network-down
conditions but the socket reports it is not closed and it is still connected.
We allowed the network to be down for over 45 minutes and this condition
persisted for the entire time.
> Improve CQ performance under flaky network conditions
> -----------------------------------------------------
>
> Key: GEODE-3948
> URL: https://issues.apache.org/jira/browse/GEODE-3948
> Project: Geode
> Issue Type: Improvement
> Components: cq, messaging
> Reporter: Galen O'Sullivan
> Assignee: Galen O'Sullivan
> Priority: Minor
>
> Client CQ connections occasionally stop receiving messages and become blocked
> indefinitely.
> This can be caused by a server that hangs or dies without sending a close
> message, or by some firewalls.
> The client already gets ping messages from the server, but currently ignores
> them. Let's use those messages to detect a failed connection and close it.
> Probably the client should follow the same logic and send ping messages if it
> has sent no acks for a while, so that the server can also detect and close a
> broken connection.
> The timeout could be specified as a number and time interval, the ping
> interval and the number of missed pings after which to fail.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
