curator-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From dragonsinth <>
Subject [GitHub] curator pull request: TreeCache should inform listeners when its f...
Date Wed, 22 Jul 2015 21:44:22 GMT
Github user dragonsinth commented on a diff in the pull request:
    --- Diff: curator-recipes/src/main/java/org/apache/curator/framework/recipes/cache/
    @@ -69,6 +69,9 @@
              * While the connection is down, the TreeCache will continue to have its state
from before it lost
              * the connection and after the connection is restored, the TreeCache will emit
normal child events
              * for all of the adds, deletes and updates that happened during the time that
it was disconnected.
    +         * </p><p>
    +         * After reconnection, the cache will resynchronize its internal state with the
server, then fire a
    +         * {@link #INITIALIZED} event.
              * </p>
    --- End diff --
    I don't *think* so since that can be an extremely transient failure, and wouldn't cause
ephemeral nodes to disappear.  Based on my testing this with ssh tunnels that I'd drop and
then recreate, I'd see SUSPENDED immediately but only see LOST much later.

If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at or file a JIRA ticket
with INFRA.

View raw message