curator-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <>
Subject [jira] [Commented] (CURATOR-247) Extend Curator's connection state to support SESSION_LOST
Date Mon, 24 Aug 2015 02:06:48 GMT


ASF GitHub Bot commented on CURATOR-247:

Github user Randgalt commented on the pull request:
    This is hilarious. In July 2013, I submitted a patch to add some testable hooks to ZooKeeper.
I forgot all about it was never touched (
Well, it's now merged in to ZK 3.5 and, guess what, it has a SESSION expiration injection
method! This is Twilight Zone level stuff. I was on my computer writing a hack to inject the
session event and digging into ZooKeeper source when I saw what looked like my code. Imagine
my surprise...

> Extend Curator's connection state to support SESSION_LOST
> ---------------------------------------------------------
>                 Key: CURATOR-247
>                 URL:
>             Project: Apache Curator
>          Issue Type: Sub-task
>          Components: Framework
>    Affects Versions: 2.8.0
>            Reporter: Jordan Zimmerman
>            Assignee: Jordan Zimmerman
>             Fix For: 3.0.0
> Currently, Curator has a connection state for LOST that confuses users. It does _not_
mean that the session is lost. Instead it means that the retry policy has given up retrying.
Introduce a new connection state that roughly corresponds to the ZooKeeper session expiring.
Possibly require that clients request this support via a new new builder method in CuratorFrameworkFactory

This message was sent by Atlassian JIRA

View raw message