geode-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dan Smith (JIRA)" <j...@apache.org>
Subject [jira] [Created] (GEODE-3984) Protobuf client gets disconnected after a minute of inactivity, no ping message to keep the socket alive
Date Thu, 16 Nov 2017 01:21:00 GMT
Dan Smith created GEODE-3984:
--------------------------------

             Summary: Protobuf client gets disconnected after a minute of inactivity, no ping
message to keep the socket alive
                 Key: GEODE-3984
                 URL: https://issues.apache.org/jira/browse/GEODE-3984
             Project: Geode
          Issue Type: Bug
          Components: client/server
            Reporter: Dan Smith


Clients connecting using the new protocol will have their sockets closed after 60 seconds
by the client health monitor.

However, there is no ping message that the client can use to keep the socket alive. It's also
unclear if a client needs to be actively using every connection it makes to the server? The
old protocol allowed the client to ping on one connection to keep all connections alive with
the client health monitor.

Do we expect clients to reconnect every time they have been idle for a minute? If so, we need
to document that. If not, we need to provide an easy way for clients to keep their connections
alive.

{noformat}
[warning 2017/11/15 16:37:05.391 PST server1 <ClientHealthMonitor Thread> tid=0x47]
Monitoring client with member id identity(localhost<ec>:60920,connection=1. It had been
60,874 ms since the latest heartbeat. Max interval is 60,000. Terminated client.
{noformat}



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Mime
View raw message