zookeeper-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Enrico Olivelli (Jira)" <j...@apache.org>
Subject [jira] [Updated] (ZOOKEEPER-922) enable faster timeout of sessions in case of unexpected socket disconnect
Date Fri, 06 Sep 2019 15:45:05 GMT

     [ https://issues.apache.org/jira/browse/ZOOKEEPER-922?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Enrico Olivelli updated ZOOKEEPER-922:
--------------------------------------
    Fix Version/s:     (was: 3.5.6)

> enable faster timeout of sessions in case of unexpected socket disconnect
> -------------------------------------------------------------------------
>
>                 Key: ZOOKEEPER-922
>                 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-922
>             Project: ZooKeeper
>          Issue Type: Improvement
>          Components: server
>            Reporter: Camille Fournier
>            Assignee: Camille Fournier
>            Priority: Major
>             Fix For: 3.6.0, 3.5.7
>
>         Attachments: ZOOKEEPER-922.patch
>
>
> In the case when a client connection is closed due to socket error instead of the client
calling close explicitly, it would be nice to enable the session associated with that client
to time out faster than the negotiated session timeout. This would enable a zookeeper ensemble
that is acting as a dynamic discovery provider to remove ephemeral nodes for crashed clients
quickly, while allowing for a longer heartbeat-based timeout for java clients that need to
do long stop-the-world GC. 
> I propose doing this by setting the timeout associated with the crashed session to "minSessionTimeout".



--
This message was sent by Atlassian Jira
(v8.3.2#803003)

Mime
View raw message