curator-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mike Drob (JIRA)" <>
Subject [jira] [Commented] (CURATOR-218) TreeCache initialization problem with non existant root path
Date Wed, 08 Jul 2015 15:57:04 GMT


Mike Drob commented on CURATOR-218:


In {{ConnectionState.process}}, we call all the {{parentWatcher.process}} before setting our
own connected state. One of the parent watchers is from {{CuratorFrameworkImpl}} and that's
the one that triggers {{ConnectionStateManager}} to stop blocking. I _think_ that we can swap
the order of those operations, but I'm not 100% sure it won't impact reconnect or connection
loss somewhere else. Anyway, running the full test suite now and if that passes then I will
put up a PR.

> TreeCache initialization problem with non existant root path
> ------------------------------------------------------------
>                 Key: CURATOR-218
>                 URL:
>             Project: Apache Curator
>          Issue Type: Bug
>          Components: Recipes
>    Affects Versions: 2.7.0, 2.7.1, 2.8.0
>         Environment: host: AWS EC2 t2.medium type
> uname -a = Linux bamboo-agent 3.13.0-44-generic #73-Ubuntu SMP Tue Dec 16 00:22:43 UTC
2014 x86_64 x86_64 x86_64 GNU/Linux
> lsb_release -a = 
> Distributor ID:	Ubuntu
> Description:	Ubuntu 14.04.1 LTS
> Release:	14.04
> Codename:	trusty
> ZK version: is a curator TestingServer
> java: java 8
> maven: 3.2.5
>            Reporter: Samuel García Martínez
>            Assignee: Scott Blum
>         Attachments: failing_test.txt
> I'm implementing a Guava service relying on the startAsync feature. I'm using a listener
to wait for the INITIALIZED event to fire the guava service notifyStarted method, but sometimes
the listener never receives the event if the root path does not exist.
> I've created a repository with a failing test (looping over the failing test to force
> repo with tests:
> failing test: mvn -Dtest=TreeCacheTest#testListenerNonExistentRootLoop test

This message was sent by Atlassian JIRA

View raw message