curator-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Purshotam Shah (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (CURATOR-334) Curator doesn't retry on GC pause
Date Wed, 01 Jun 2016 17:58:59 GMT

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

Purshotam Shah updated CURATOR-334:
-----------------------------------
    Description: 
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.

> Curator doesn't retry on GC pause
> ---------------------------------
>
>                 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)

Mime
View raw message