curator
curator copied to clipboard
apache
Apache Curator
ServiceDiscoveryImpl.reRegisterServices() can be trigger on ConnectionState events: RECONNECTED and CONNECTED. Causing the reRegisterServices() method to be run on ConnectionStateManager thread. If a connection drops while running reRegisterServices() it will be...
I think it's reasonable to receive the added/deleted service instance when ServiceCacheListener is notified, currently ServiceCacheListener only has one no-arg method: public void cacheChanged(); Maybe we should add(or replace with)...
When a curator operation thread is interrupted, some classes (PersistentNode ConnectionState primarily) report the interruption in two ways at the same time - by re-marking the thread interruption status and...
[CURATOR-353] PathChildrenCache and PersistentNode interrupt each other if sharing the same executor
In our example, we've got a PathChildrenCache and PersistentNode sharing the same executor. This interacts badly with interrupts - when PathChildrenCache is closed, this calls CloseableExecutorService.close(), which interrupts all the...
The read requests fail when connecting to a read only ensemble. I made a class for this using TestingCluster, but it requires to set iptables rules in order to mimic...
Hi, I'm trying to upgrade the curator framework from 2.6.0 to 2.7.1, but I'm having some problems. In the 2.6.0 version almost everything works fine, but the ServiceDiscovery.updateService() that is...
Consider the following: lock is being acquired by main thread but released by another thread. This throws an exception: java.lang.IllegalMonitorStateException: You do not own the lock: /locks/abc at org.apache.curator.framework.recipes.locks.InterProcessMutex.release(InterProcessMutex.java:140) Are...
This is potentially a bug in Curator 2.7.1 where LeaderSelector's getParticipants() reports one less participants than the actual number. On the node missing from the result of getParticipants(), I found...
Current schema violations look like this: Schema violation: Data is not valid for schema: Schema{name='950eb5e3-b64f-43a4-833e-4262be0f3018', pathRegex=/clusters/.*, path='null', documentation='', dataValidator=InternalSchemaValidator(List(root, ip, readonly)), ephemeral=CAN, sequential=CAN, watched=CAN, canBeDeleted=true, metadata={*=1, allocators=1}} It lacks information...
If you try to create a schema for "/", it gets converted to "" due to bug in Schema.fixPath() --- Originally reported by randgalt, imported from: Not possible to create...