You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Andrey Kuznetsov (JIRA)" <ji...@apache.org> on 2018/09/25 12:51:00 UTC

[jira] [Commented] (IGNITE-9683) Create manual pinger for ZK client

    [ https://issues.apache.org/jira/browse/IGNITE-9683?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16627284#comment-16627284 ] 

Andrey Kuznetsov commented on IGNITE-9683:
------------------------------------------

[~Jokser], Zookeeper docs [1] mention ping requests built into Zk client:

{noformat}
The session is kept alive by requests sent by the client. If the session is idle for a period of time that would timeout the session, the client will send a PING request to keep the session alive. This PING request not only allows the ZooKeeper server to know that the client is still active, but it also allows the client to verify that its connection to the ZooKeeper server is still active. The timing of the PING is conservative enough to ensure reasonable time to detect a dead connection and reconnect to a new server.
{noformat}

Is this statement outdated, or "reasonable time" is not suitable for Discovery SPI?


> Create manual pinger for ZK client
> ----------------------------------
>
>                 Key: IGNITE-9683
>                 URL: https://issues.apache.org/jira/browse/IGNITE-9683
>             Project: Ignite
>          Issue Type: Improvement
>          Components: cache, zookeeper
>    Affects Versions: 2.5
>            Reporter: Pavel Kovalenko
>            Priority: Major
>             Fix For: 2.7
>
>
> Connection loss with Zookeeper more than ZK session timeout for server nodes is unacceptable. To improve durability of connrction, we need to keep session with ZK as long possible. We need to introduce manual pinger additionally to ZK client  and ping ZK server with simple request each tick time.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)