Re: [E] Curator, Zookeeper and Guava woes (again)

work, > curator-x-discovery, etc.? An official fork would be better than an internal > fork. > > On Tue, Dec 14, 2021 at 2:51 AM Jordan Zimmerman <mailto:jor...@jordanzimmerman.com>> wrote: >> Is there a way out of this situation without deploying our own >> custom-pa

Re: Curator, Zookeeper and Guava woes (again)

> Is there a way out of this situation without deploying our own custom-patched > Curator 2 or Curator 3 in which we remove Guava dependencies? Merely > upgrading to Guava 17 isn't much of a win for us (and meanwhile our automated > security scanners keep yelling at us for using outdated

Re: [External Sender] Double Leadership Issue

It would be better if these test cases are turned into unit tests so we can have them in the code base to prevent future problems. Can you please turn them into Unit Tests? -Jordan > On Nov 6, 2021, at 8:52 PM, Viswanathan Rajagopal > wrote: > > Have linked the test cases in my original

Re: [External Sender] Double Leadership Issue

ed by >>* setLeadership(false) The problem here is that deletion isn't guaranteed here. It could happen at a later time when there are network partitions. -Jordan > On Nov 3, 2021, at 3:33 PM, Viswanathan Rajagopal > wrote: > > Hi Jordan, > > The dual leadershi

Re: Double Leadership Issue

Do I understand this correctly that there are two leaders for a short period of time - i.e. it corrects itself eventually? Or does the dual leadership continue indefinitely? -Jordan > On Nov 2, 2021, at 11:48 AM, Viswanathan Rajagopal > wrote: > > Hello Team, > > Greetings! > Any update on

Re: LeaderSelector Recipe Can Result In Orphaned Ephemeral Nodes And No Leader Election

hsbugreports/zookeeper_test > <https://github.com/hsbugreports/zookeeper_test> > > Thanks. > -hs > >> On Jul 30, 2021, at 2:32 PM, Jordan Zimmerman > <mailto:jor...@jordanzimmerman.com>> wrote: >> >> A quick thought... I wonder if we need

Re: LeaderSelector Recipe Can Result In Orphaned Ephemeral Nodes And No Leader Election

current.FutureTask.run(FutureTask.java:266) [?:?] > at > java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) > [?:?] > at > java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) > [?:?] > at java.lang.Thread.run(Thread.java:

Re: [External Sender] Double Locking Issue

would reject the write on the now expired ZNode. So, the lock recipe would be enhanced so that it tries to do a setData on the node before it accepts that is has the lock. Just a thought. > On Jul 30, 2021, at 9:54 AM, Jordan Zimmerman > wrote: > > Even more... actually, this sh

Re: [External Sender] Double Locking Issue

and interrupts the thread already via notifyAll(). So, again, sorry for the noise. I'll go over the scenario again to see if I have more comments. -Jordan > On Jul 30, 2021, at 9:18 AM, Jordan Zimmerman > wrote: > > Actually... I'm looking at LockInternals and it already has a

Re: [External Sender] Double Locking Issue

, interrupt the thread. This will cause wait() to throw InterruptedException and then the lock node will be deleted. -Jordan > On Jul 30, 2021, at 9:11 AM, Jordan Zimmerman > wrote: > > Making lock code watch its lock node it has created > > I don't think this is useful. Once th

Re: [External Sender] Double Locking Issue

code is well protected to cover this zookeeper race condition, > because Leader Latch code internally handle the connection events (which they > use to interrupt latch_acquire_state to reset its latch every time connection > is reconnected), means it will explicitly release th

Re: LeaderSelector Recipe Can Result In Orphaned Ephemeral Nodes And No Leader Election

Curator has a feature called "protected mode". It adds a UUID to the node name and when there is connection issue or other connection it tries to find the node it created (see here:

Re: [External Sender] Double Locking Issue

g cleaned up by the server as part of > previous session cleanup activities. > I am NOT seeing a Curator bug here, but looking out for suggestions / > recommendations in handling this zookeeper race condition. Either can a > feature be added to Curator to cover this case / any recomm

Re: Double Locking Issue

A few more things... > Based on our initial analysis and few test runs, we saw that Curator > acquire() method acquires the lock based on “about to be deleted lock node of > previous session”. Explanation : Ephemeral node created by previous session > was still seen by client that reconnected

Re: CuratorCache and sub path's

, submitting upstream PR’s is something I’d certainly be willing to do! > > /Ryan > >> On Jun 29, 2021, at 7:30 AM, Jordan Zimmerman >> wrote: >> >> Hi, >> >> Unfortunately, CuratorCache has not been testing in real world scenarios >> very

Re: CuratorCache and sub path's

Hi, Unfortunately, CuratorCache has not been testing in real world scenarios very much. So, these may actually be bugs. If it's not behaving as you think it should please open an issue and hopefully a PR. If you're unable to write the PR maybe I or one of the other committers can get to it.

[ANNOUNCE] Enrico Olivelli is the new PMC Chair

the Chair since May of 2013 - that's a long time :D I'm thrilled to pass the "gavel" to Enrico. I'm not going anywhere and will still contribute as I can to the project. Sincerely, Jordan Zimmerman

Re: Curator PersistentNode recipe

Yes - the node is deleted ala: client.delete().guaranteed().forPath(localNodePath); So, if the connection is currently lost the path is added to an internal queue and deleted when the connection is repaired. -Jordan > On Oct 3, 2020, at 12:17 PM, evaristo.camar...@yahoo.es wrote: > >

Re: REOPEN CURATOR-538?

I could've sworn we addressed this as part of 5.0 - I'll do some research or maybe someone else can comment. -JZ > On Jul 23, 2020, at 11:53 AM, evaristo.camar...@yahoo.es wrote: > > Hi there, > > I propose to re-open Curator - 538 > > [CURATOR-538] Background exception was not retry-able or

Re: Curator - Zookeeper compatibility

4.3.0 will work. We should updated the website. > On Jun 11, 2020, at 10:12 AM, Borja Bravo Alférez wrote: > > Dear Curator community, > > I have a question about the Curator - Zookeeper compatibility with Zookeeper > 3.4.x. Could I use Curator 4.3.0 with it? > > For one side there is this

Re: CURATOR-569 MISSING IN CURATOR 5.0.0 RELEASE NOTES

Fixed > On Jun 1, 2020, at 10:25 AM, evaristo.camar...@yahoo.es wrote: > > Hi there, > > I saw that Curator-569 issue was added to 5.0.0 release, but it is missing in > release notes. > > Regards, > > /Evaristo

Re: Curator 5.0 binary compatibility

ity issue. > > I have also run locally tests of the staged sources. > I am casting my +1 > > I think that this discussion as been useful for the community > > Thank you > Enrico > > Il giorno mer 27 mag 2020 alle ore 00:55 Jordan Zimmerman < > jor...@jord

Re: Curator 5.0 binary compatibility

7, 2020 at 6:32 AM Enrico Olivelli <mailto:eolive...@gmail.com>> wrote: > >> >> >> Il giorno mar 26 mag 2020 alle ore 21:53 Jordan Zimmerman < >> jor...@jordanzimmerman.com> ha scritto: >> >>> The initial email is almost a week old. I post

Re: Curator 5.0 binary compatibility

to. -JZ > On May 25, 2020, at 9:10 AM, Jordan Zimmerman > wrote: > >> If most of the problem is about ListenerContainer, don't we have a way to >> keep it and emulate it using and implementation based on the new API ? > > > Unfortunately not. The issue is that it

Re: Curator 5.0 binary compatibility

020, at 1:33 AM, Enrico Olivelli wrote: > > Il giorno dom 24 mag 2020 alle ore 23:17 Jordan Zimmerman < > jor...@jordanzimmerman.com <mailto:jor...@jordanzimmerman.com>> ha scritto: > >> Enrico, >> >> It reminds me of the breaking changes in Guava

Re: Curator 5.0 binary compatibility

the packages and start a brand new system. > > This approach was done in Apache Commons and IIRC it will be done with > > Netty5. We also did it with the new Apache Bookkeeper API. > > > > Pros: > > No need to preserve compatibility, we are free to clean up all of t

Re: Curator 5.0 binary compatibility

t; >> Pros: >> No need to preserve compatibility, we are free to clean up all of the tech >> debt. >> The switch to Curator 5 will be explicit opted in >> >> Cons: >> Cherry picks won't be straightforward. >> >> Enrico >> >

Re: Curator 5.0 binary compatibility

"hack". Can anyone think of one? I'd really appreciate people testing with it. Try a build with just Curator 5.0 and then install and include this curator-5_0-test:combo:1.0-SNAPSHOT early in the CLASSPATH - it should work. -Jordan > On May 21, 2020, at 10:43 AM, Jordan Zimmerman

Curator 5.0 binary compatibility

Hello All, Sorry for the cross-posting but this is important enough to justify it. Apache Curator is in the process of releasing version 5.0. We've taken the opportunity to address some long standing tech debt but this causes breaking changes. We've detailed the breaks here:

Re: UTILITY TO HANDLE ZNODE PATHS WITH PROTECTED MODE

It's OK with me. Open an issue and create a PR. -JZ > On May 9, 2020, at 2:43 AM, evaristo.camar...@yahoo.es wrote: > > Hi there, > We are using Curator + Zookeeper in a manner that our ZNode paths contain > meaningful information. > > The model is like: > > /root/report/ > /root/report/R1 >

Re: CURATOR WITH MULTIPLE ZK SERVERS

ratorFrameworkFactory.Builder. What do you think is best? Do you still > believe that is worthy to extend the builder? > > Thanks, > > /Evaristo > > > En domingo, 3 de mayo de 2020 20:09:04 CEST, Jordan Zimmerman > escribió: > > > Try it and

Re: CURATOR WITH MULTIPLE ZK SERVERS

> @Override > public boolean updateServerListEnabled() > { > return false; > } > } > Thanks in advance, > /Evaristo > > > En viernes, 1 de mayo de 2020 19:33:15 CEST, evaristo.camar...@yahoo.es > escribió: > > > Thx Jordan. I wi

Re: Dealing with eventual consistency

That part is true I'm not sure how much use it is though. If there are multiple writers you can't know what the latest version is - there may be other servers writing that have been seen yet. But, then, I probably don't completely understand the use case. -JZ > On May 2, 2020, at 9:35 AM,

Re: Dealing with eventual consistency

You can still miss a pending write on the client. Just because you read N from the ZNode doesn't mean that that's it's real value on the leader. The only way in ZooKeeper to be certain is to do a write as those always take place on the leader. -Jordan > On May 1, 2020, at 5:51 PM, Scott Blum

Re: Dealing with eventual consistency

for the system in question it's ugly. I need to make it look > pretty :-) > > ~ David > > > On Fri, May 1, 2020 at 11:46 AM Jordan Zimmerman <mailto:jor...@jordanzimmerman.com>> wrote: >> I'm aware a znode or perhaps pzxid (for a path of data) could be passed to &g

Re: CURATOR WITH MULTIPLE ZK SERVERS

new option that is a bit misleading. > - Option 2 has a more clear API in my view, if FixedEnsembleProvider is used > with updateServerList set to false, then EnsembleTracker can ignore updating > the connecstring. > > Regards, > > /Evaristo > > > En vier

Re: CURATOR WITH MULTIPLE ZK SERVERS

I think this might be a bug or maybe an oversight. It looks like the EnsembleTracker gets enabled regardless of the mode that Curator is in: see CuratorFrameworkImpl's constructor where it allocates an EnsembleTracker. You could open a PR that makes this optional. -Jordan > On Apr 30, 2020,

Re: Dealing with eventual consistency

> I'm aware a znode or perhaps pzxid (for a path of data) could be passed to > the second machine. It's available to the client. See: https://github.com/apache/zookeeper/blob/master/zookeeper-server/src/main/java/org/apache/zookeeper/ClientCnxn.java#L810 You'd create your own ZooKeeper

Re: Handle retriable exception?

Yeah - I think that part of the code (and several others) need a re-think. We have the opportunity right now as we're going to do 5.0. I'm amenable to holding off and changing whatever we think can be improved. -Jordan > On Apr 24, 2020, at 10:12 PM, tison wrote: > > Hi curators, > > It

Re: Release of 5.0?

3, 2020 at 7:45 AM Cameron McKenzie <mailto:mckenzie@gmail.com>> wrote: > I'm happy for a release. I can do it the build if no one else has time. > cheers > > On Thu, Apr 23, 2020 at 7:25 AM Jordan Zimmerman <mailto:jor...@jordanzimmerman.com>> wrote: > Hi Fol

Release of 5.0?

Hi Folks, Are we ready for a 5.0 release? I think we have a good working set for it. Speak now if you want anything else in this release. If no one speaks up, I'll start on it soon (unless one of the other committers wants to run it - let me know). -Jordan

Re: Help with apache curator 4.3.0

sk questions/clarify my doubts? > > -sr > > On Sun, 5 Apr 2020 at 21:20, Jordan Zimmerman <mailto:jor...@jordanzimmerman.com>> wrote: > Yes, dynamic reconfig is supported in Curator 4.x. There are no examples > because it's really a ZooKeeper feature, not a Curator f

Re: Help with apache curator 4.3.0

Yes, dynamic reconfig is supported in Curator 4.x. There are no examples because it's really a ZooKeeper feature, not a Curator feature. Curator's DSL has a reconfig() method, etc. Curator also listens for dynamic ensemble changes. -Jordan > On Apr 3, 2020, at 1:29 AM, Suhas S R wrote: > >

Re: SSL Verifier issue with Curator 4.2 and ZK 3.5.6

The reasoning is lost to history. I think Ioannis worked on that feature. In any event, a PR that makes configToConnectionString() non-static and overridable would be a nice addition I think. Please open an Jira Issue and a PR. -Jordan > On Apr 1, 2020, at 6:15 PM, Joe Ammann wrote: > > Hi

Re: [CURATOR-549] Recipes based on Persistent Recursive Watchers needs more reviews

Hi Folks Any objection to merging this tomorrow? Do you need more time Shay? -Jordan P.S. I hope everyone is staying well in this trying time > On Mar 27, 2020, at 4:57 PM, Jordan Zimmerman > wrote: > > Hi Folks > > Another plea for more reviews on this > https://gith

[CURATOR-549] Recipes based on Persistent Recursive Watchers needs more reviews

Hi Folks Another plea for more reviews on this https://github.com/apache/curator/pull/335 - this will become the new caching recipe for Curator folks. Here's your opportunity to have input on it. -Jordan

New Persistent/Recursive watcher recipes - needs reviews

Hi Folks, Here are the new recipes based on Persistent/Recursive Watchers. There's a new PersistentWatcher recipe and a brand new implementation of a cache, CuratorCache that replaces all the existing cache recipes. Reviews would be appreciated. https://github.com/apache/curator/pull/335

Re: PROPOSAL: Curator 5.0

y <mailto:shays...@gmail.com>> ha scritto: > Sorry for the late reply. > +1 from me too. > > On Wed, Mar 4, 2020, 04:37 Jordan Zimmerman <mailto:jor...@jordanzimmerman.com>> > wrote: > > > Hi Folks, > > > > I mentioned this a while back, but no

PROPOSAL: Curator 5.0

Hi Folks, I mentioned this a while back, but now the ZooKeeper 3.6.0 is out I'd like to make it official. I propose we move to Curator 5.0 and apply a few non-backward compatible changes - i.e. take the opportunity to fix some tech debt. See CURATOR-558

Re: Curator listener issue

hats what exactly I also thought so I put a sleep with 10 seconds before > calling shutting down and closing the curator instance but it did not change > the behaviour. > > On Wed, Feb 26, 2020 at 3:30 PM Jordan Zimmerman <mailto:jor...@jordanzimmerman.com>> wrote: >

Re: Curator listener issue

} > } > > private final void handleTakeSingletonRole() throws Exception { > > _logger.info("handleTakeSingletonRole: Received Singleton Role."); > > // We have just become the Singleton Server. Ha! > try { > while (true)

Re: Curator state change listener

r-LeaderSelector-0] The leader threw an exception > > Thanks > > > On Tue, Feb 25, 2020 at 7:43 PM Jordan Zimmerman <mailto:jor...@jordanzimmerman.com>> wrote: > I'd need a lot more information to understand why. I suggest you set up a > test case so we can look at it. > &

Re: Curator state change listener

gt; On Tue, Feb 25, 2020, 6:32 PM Jordan Zimmerman <mailto:jor...@jordanzimmerman.com>> wrote: > There's really only 1 ZooKeeper instance? If so, it's not possible that > Curator won't report SUSPENDED and then LOST. If you have more than 1 > ZooKeeper instance, how do you know bot

Re: Curator state change listener

There's really only 1 ZooKeeper instance? If so, it's not possible that Curator won't report SUSPENDED and then LOST. If you have more than 1 ZooKeeper instance, how do you know both clients are connecting to the same instance? Likely they're not. -Jordan > On Feb 25, 2020, at 1:27 PM, Arpit

Re: ZookKeeper 3.5.7

https://github.com/apache/curator/pull/346 > On Feb 17, 2020, at 11:13 PM, Cameron McKenzie wrote: > > Yep, agreed. > > On Tue, Feb 18, 2020 at 3:01 PM Jordan Zimmerman <mailto:jor...@jordanzimmerman.com>> wrote: > Hey Cameron, > > Let's wait for CURATOR-55

Re: ZookKeeper 3.5.7

Hey Cameron, Let's wait for CURATOR-559 <https://issues.apache.org/jira/browse/CURATOR-559> - I think this needs immediate fixing. Very surprising we haven't heard about this before. -Jordan > On Feb 17, 2020, at 8:29 AM, Jordan Zimmerman > wrote: > > Sounds go

Re: ZookKeeper 3.5.7

t the next version will likely be Curator 5.0. > Anyone want to run the release? Or I can do it. > > > Jordan Zimmerman

ZookKeeper 3.5.7

it. Jordan Zimmerman

Re: Update ACL of a znode

Yes. Curator supports all of ZooKeeper’s APIs. CuratorFramework has a setAcl() DSL method. Jordan Zimmerman > On Jan 18, 2020, at 1:57 PM, Arpit Jain wrote: > >  > Hi, > > Is it possible to update ACL of an already created znode using curator API? > > Thanks

Re: Curator client for SASL authentication

I saw the conversation in the zookeeper list. I’m traveling at the moment. If someone else doesn’t get to this. I’ll check when I can. Jordan Zimmerman > On Jan 14, 2020, at 6:05 PM, Arpit Jain wrote: > >  > Hi, > > I am using SASL Kerberos based auth

ASF Slack

Hey Folks, Apache has a Slack server. I've created a Curator channel there. Committers, in particular, please join. It will make coordination on releases/issues much easier. -Jordan ASF Slack: https://the-asf.slack.com Curator Channel: #curator

Re: Leader election and leader operation based on zookeeper

ElectionServiceNG.java > > <https://github.com/TisonKun/flink/blob/ad51edbfccd417be1b5a1f136e81b0b77401c43a/flink-runtime/src/main/java/org/apache/flink/runtime/leaderelection/ZooKeeperLeaderElectionServiceNG.java> > > Jordan Zimmerman <mailto:jor...@jordanzimmerman.com>> 于

Re: Leader election and leader operation based on zookeeper

Thinking more about this... I imagine this works if the current leader path is always used. I need to think about this some more. -JZ > On Sep 21, 2019, at 1:31 PM, Jordan Zimmerman > wrote: > > The issue is that the leader path doesn't stay constant. Every time there is

Re: Leader election and leader operation based on zookeeper

> one-shot and when perform a transaction, checking the existence of latch path > && in state LEADING. > > Given the election algorithm works, state transited to LEADING when its latch > path once became > the smallest sequential znode. So the existence of latch path guardin

Re: Leader election and leader operation based on zookeeper

> It seems Curator does not expose session id you can always access the ZooKeeper handle directly to get the session ID: CuratorFramework curator = ... curator.getZookeeperClient().getZooKeeper() -JZ > On Sep 20, 2019, at 10:21 PM, Zili Chen wrote: > > >>I am assuming the "write operation"

Re: Enable configuration to replace usage of RetryLoop with SessionFailRetryLoop

Yes, I think so. It's been a very long time since I've looked at SessionFailRetryLoop and it was written by someone other than me. But, the general answer is this: The ConnectionHandlingPolicy controls how the retry loop handling is done. See, StandardConnectionHandlingPolicy.java. You can

Re: Concurrent createContainers

Yeah - that would be something else as you correctly note ZKPaths catches KeeperException.NodeExistsException internally. > On Sep 11, 2019, at 9:48 PM, Zili Chen wrote: > > I notice that methods mentioned above internally call ZKPaths.mkdirs which > tolerates

Re: LeaderLatch recipe could run into two leaders

ath(ourPath), which would be like > > curatorFramework.inTransaction() > .check().forPath(election-node-path).and() > .setData().forPath(...).and().commit(); > > to overcome this edge case. > > Best, > tison. > > > Jordan Zimmerma

Re: [DISCUSS] CURATOR-533

recently, I don't > imagine it has had a lot of uptake, but it may be worth asking the question > on the curator-user list to work out if there's going to be any impact in > removing the existing implementation? > cheers > > On Mon, Jul 29, 2019 at 2:50 AM Jordan Zimmerman

Re: Improving exception classification for retries

> what would you say about making it fully spring-retry based I'm -1 on adding a dependency to Spring. > contributing some improvements about Curator's retry logic That would be great and very much appreciated. > What is your policy on breaking changes? We've always tried to be backward

Re: Curator client getting suspended before zookeeper session timeout

"Suspended" is sent as soon as the connection is lost. "Lost" is sent when the session timeout expires. This is documented here: http://curator.apache.org/errors.html (see Notifications). Also, this Tech Note has some details:

Re: LeaderLatch recipe could run into two leaders

What Cameron writes is correct. The only other thing to be concerned with is large GC times and small session times. We have a Tech Note on this: https://cwiki.apache.org/confluence/display/CURATOR/TN10 -Jordan > On Mar 27, 2019, at

[ANNOUNCE] Apache Curator 4.2.0 released

Hello, The Apache Curator team is pleased to announce the release of version 4.2.0. Apache Curator is a Java/JVM client library for Apache ZooKeeper[1], a distributed coordination service. Apache Curator includes a high-level API framework and utilities to make using Apache ZooKeeper much

Re: LeaderLatch random selection

> the order in which the participants contend for the lock The order that processes contend is essentially random. Whichever client connects first gets the next ephemeral node. It's not deterministic. -JZ > On Feb 27, 2019, at 2:55 PM, Patrick Peralta wrote: > > Hello! > > I have a question

[DISCUSS] Release 4.2.0

Hey, CURATOR-498 is a critical problem and needs to be released ASAP. So, I'd like to prep a release of 4.2.0. There's not much else in this release (CURATOR-505 is new). If anyone wants anything else in 4.2.0 speak up now and act on the corresponding open PR. -Jordan

IMPORTANT CURATOR-498

A very serious edge case has been discovered and is described in http://issues.apache.org/jira/browse/CURATOR-498 . There is a PR for it now: https://github.com/apache/curator/pull/299 . The fix in

Re: Release 4.1.0 planning

and the inners of curator to improve the test but desisted after some > time. Currently we patch it locally on our systems. > > Anyway thanks for the work and it is nice to see that Curator is alive and > healthy > > Regards, > > Borja > > On Thu, Dec 6, 2018 at 7:

Re: Possible deadlock in blockUntilConnected?

uratorFrameworkFactory.newClient( > zooKeeperHost + ":" + zooKeeperPort, > Integer.MAX_VALUE, > Integer.MAX_VALUE, > new RetryForever(1000)); > > client.start(); > client.blockUntilConnected(); > > On Fri, Dec 7, 2018 at 5

Re: Possible deadlock in blockUntilConnected?

There isn't much to go on in your description. Please send some sample code, logs, possibly a thread dump. Maybe send your test program. One thing that sticks out is that you say each thread has its own Curator client. Why is that? You only need 1 Curator client per ZK ensemble in a VM.

Re: typed model with multiple classes

No, not today. You would create two models, one for the /groups/{groupId} model and one for the user. -JZ > On Sep 7, 2018, at 12:31 PM, Hendrik Haddorp wrote: > > Hi, > > is it possible to create a typed model that contains hierarchical objects of > different types? For example if I have

Re: org.apache.curator.x.async.modeled.details.CachedModeledFrameworkImpl.children()

Wow - I think this is a bug. If you don't mind, please open an issue in Curator's Jira > On Sep 7, 2018, at 8:02 AM, Hendrik Haddorp wrote: > > Hi, > > org.apache.curator.x.async.modeled.details.CachedModeledFrameworkImpl.children() > and >

Re: Rationale for CuratorFramework default value

ng the Curator guy ;-) > > I've found a few other places where some defensive constructs could be > avoided or things could be optimized, I'll prepare a PR with these soon. > > Sylvain > > Le 29/08/2018 à 17:45, Jordan Zimmerman a écrit : >> Hi Sylvain :D - I hope al

Re: Rationale for CuratorFramework default value

Hi Sylvain :D - I hope all is well at Elastic > I just found out that the default value for > `CuratorFrameworkImpl.getDefaultData()` is the string representation of the > local IP address [1]. As I recall, it was done as a debugging aid. Putting the IP address allows someone to know which

Re: NodeCacheListener Fails to Get Called

observed that only some NodeCacheListeners > got invoked while others did not. > > wangchunc...@outlook.com <mailto:wangchunc...@outlook.com> > > From: Jordan Zimmerman <mailto:jor...@jordanzimmerman.com> > Date: 2018-07-17 03:06 > To: user <mailto:user@curator.apache.org

[DISCUSS] Moving to Java 8

Hey Folks, Any objects to making Java 8 the minimum for Curator? ZooKeeper is now Java 8 minimum. I've opened an issue to do this: https://issues.apache.org/jira/browse/CURATOR-471 If I don't here any objects by the end of the week I'll

Re: InterProcessMutex error handling

TBH - I don't know why we never created a utility to automate this. We should add a "LockConnectionStateListener" or something that listens for connection state changes and tries to interrupt the locked thread when there's an issue. Until we have that though, you'd have to do this manually. We

Re: Unexpected session expired event

We'd need to see the ZooKeeper logs to know why you're losing your session. Also, you may have more luck on the ZooKeeper mailing list. -Jordan > On Mar 29, 2018, at 6:27 AM, Cameron McKenzie wrote: > > hey Joe, > Curator just wraps up the Zookeeper client. It is

Re: Connection Factories for Curator / Zookeeper / HTTP Tunneling

I don't know much about Cloud Foundry but how does it handle things like replicated databases, etc.? There are copious systems that don't do HTTP. > On Mar 3, 2018, at 10:13 AM, Chris Miles wrote: > > Thanks Jordan, > > It is a cloud-foundry cloud, the network

Re: Connection Factories for Curator / Zookeeper / HTTP Tunneling

Curator wraps the built-in ZooKeeper client, so Curator doesn't give you any benefit that isn't already present in ZooKeeper itself. You can easily use port 80 or 443 as the ZK/Curator client port. But, the ZooKeeper protocol (jute) is of course not HTTP. If the Firewall is expecting HTTP it

[ANNOUNCE] Apache Curator 4.0.1 released

Hello, The Apache Curator team is pleased to announce the release of version 4.0.1. Apache Curator is a Java/JVM client library for Apache ZooKeeper[1], a distributed coordination service. Apache Curator includes a high-level API framework and utilities to make using Apache ZooKeeper much easier

Re: [RELEASE] Release this week?

I've gotten no feedback on this so I'm going to start a release sometime today. Please speak now if want any last minute PRs merged before the release. -Jordan > On Feb 4, 2018, at 9:38 AM, Jordan Zimmerman <jor...@jordanzimmerman.com> > wrote: > > Hey Folks, > >

[RELEASE] Release this week?

Hey Folks, I'd like to put together a release for this coming week. If there are any issues committers/interested parties are working on that should be in the release please complete them now, -Jordan

Re: Hello - (How to use LeaderLatch in PathChildrenCacheListener)

Moving to @users... There's not enough of a code snippet to answer properly. However, I'd use a LeaderSelector instead and allocate/use the PathChildrenCache inside of it. -Jordan > On Dec 21, 2017, at 5:12 AM, 習慣/zt①个 <381954...@qq.com> wrote: > > Hello: >I'd like to launch a APP

Re: Missing event in PathChildrenCache

ZooKeeper does not guarantee that you will get every event. There are myriad ways that a client can miss events. If you are writing an application that depends on getting every event then ZooKeeper is not a good solution for you. In your example, are the create of "/test1" and the delete of

[ANNOUNCE] Apache Curator 4.0.0 released

Hello, The Apache Curator team is pleased to announce the release of version 4.0.0. Apache Curator is a Java/JVM client library for Apache ZooKeeper[1], a distributed coordination service. Apache Curator includes a high-level API framework and utilities to make using Apache ZooKeeper much easier

DISCUSS: Remove Classic connection handling

Background: We are preparing to release what will be Apache Curator 4.0.0. As usual, our tests are a bit flakey. Currently, the biggest culprit is "classic" connection handling. This is a special internal mode that most people probably don't even know about. It was added as a backward

Re: Proposal: end-of-life for Curator 2.0 and make next version 4.0.0

I've proven that it works by running all the framework/recipe tests with the latest master but forcing ZooKeeper 3.4.8 as the client library and server (via curator-test 2.12.0). > On Jul 22, 2017, at 2:55 AM, Cameron McKenzie wrote: > > Sounds ok to me as long as the

Re: Proposal: end-of-life for Curator 2.0 and make next version 4.0.0

sometime next week > if you like. > cheers > > On Thu, Jul 20, 2017 at 5:48 AM, Jordan Zimmerman <jor...@jordanzimmerman.com > <mailto:jor...@jordanzimmerman.com>> wrote: > Folks, > > I was trying to backport some PRs to CURATOR-2.0 and it was very difficu

Re: Curator support for SSL connection

Curator uses the ZooKeeper.java client internally. So, whatever that code supports, Curator supports. I don't know too much about SSL for Zookeeper. Maybe ask on the ZooKeeper list unless someone else here knows more. -Jordan > On Jun 28, 2017, at 1:36 AM, Srikanth Hugar

Re: distributed locking issue

A few things: * What's the purpose of "numLocks"? It's always 1 (as it should be) * On line 59 it should be: long end = System.nanoTime(); * System.nanoTime() "provides nanosecond precision, but not necessarily nanosecond resolution". Your lock is immediately released and, thus, you cannot

  1   2   3   >