You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@curator.apache.org by "Purshotam Shah (JIRA)" <ji...@apache.org> on 2016/06/01 17:59:59 UTC

[jira] [Updated] (CURATOR-334) Curator doesn't retry if GC pause > session timeout

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

Purshotam Shah updated CURATOR-334:
-----------------------------------
    Summary: Curator doesn't retry if GC pause > session timeout  (was: Curator doesn't retry on GC pause)

> Curator doesn't retry if GC pause > session timeout
> ---------------------------------------------------
>
>                 Key: CURATOR-334
>                 URL: https://issues.apache.org/jira/browse/CURATOR-334
>             Project: Apache Curator
>          Issue Type: Bug
>            Reporter: Purshotam Shah
>            Assignee: Jordan Zimmerman
>
> We noticed that if GC pause > session timeout and even if retry policy is set, Curator doesn't retry.
> We use CuratorFramework.getConnectionStateListenable to listen on connection state. ConnectionState.LOST is received without retry.
> Ideally, Curator should retry before notifying as connection lost.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)