Re: [VOTE] Release Apache Curator version 5.6.0

+1 binding Tests pass Hash matches Signature verifies -JZ > On Jan 2, 2024, at 4:40 PM, tison wrote: > > Hello, > > This is the vote for Apache Curator version 5.6.0 > > *** Please download, test and vote within approx. 72 hours > > Note that we are voting upon the source (tag) and

Re: [NOTICE] curator-site Git repo is created

Very nice - looks much better. > On Aug 15, 2023, at 9:17 AM, tison wrote: > > All is online now: https://curator.apache.org/ > > @kez...@gmail.com you can add yourself as a team member > to https://curator.apache.org/community/team following the instructions at >

Re: [PROPOSAL] Create curator-site Git repo

OK with me. > On Aug 14, 2023, at 7:53 AM, tison wrote: > > Hi, > > I'm building a Docusaurus-based website for Curator these days, whose first > version will be almost identical to the current one. > > With a Git-based workflow and Docusaurus-based website framework, we (or at > least I) can

Re: [VOTE] Apply a consistent code style to our codebase

+0 It's fine either way with me > On May 27, 2023, at 9:36 AM, tison wrote: > > See [1] for the discussion thread and [2] for the demo implementation. > > Briefly, I propose to adopt spotless-maven-plugin to format all our source > code with a consistent Plantir style. JIRA ticket will be

Re: [DISCUSS] Cutting a release ? 5.5.0 ?

gt;>> I agree that the next release can be 5.5.0. >>> >>> Looking forward to the next steps :) >>> >>> Best, >>> tison. >>> >>> >>> Jordan Zimmerman 于2023年4月6日周四 17:15写道： >>> >>>> OK with me >&g

Re: [DISCUSS] Cutting a release ? 5.5.0 ?

OK with me > On Apr 6, 2023, at 8:35 AM, Kezhu Wang wrote: > > The last release 5.4.0 was released on 2022.11.03, it was five month ago. > And we have accumulated at least 8 fixes, some of them are long-time > issues. I think it might be time to prepare the next release for them. > > There are

Re: [VOTE] Release Apache Curator version 5.4.0

All tests pass (Java 11, Mac OS) Signature matches Hash matches +1 Binding -Jordan Zimmerman > On Oct 21, 2022, at 8:08 AM, Enrico Olivelli wrote: > > Hello, > > This is the vote for Apache Curator version 5.4.0. > See below the list of changes, the most notable cha

Re: [VOTE] Release Apache Curator version 5.4.0

I’m away for the next few days. I can prep my vote on Monday if it isn’t too late. Jordan Zimmerman > On Oct 21, 2022, at 9:09 AM, Enrico Olivelli wrote: > > Hello, > > This is the vote for Apache Curator version 5.4.0. > See below the list of changes

Re: [RESULT] [VOTE] Release Apache Curator version 5.3.0

Thanks for running this Zili. -Jordan > On Jul 4, 2022, at 3:21 AM, tison wrote: > > The vote passes with 4 binding VOTES[1]: > > - Jordan Zimmerman > - Zili Chen (tison) > - Cameron McKenzie > - Enrico Olivelli > > I will promote the artifacts. > > T

Re: [VOTE] Release Apache Curator version 5.3.0

Hashes and Signatures match Tests succeeded though TestBoundedDistributedQueue and TestTreeCache are flakey +1 Binding -Jordan Thank you Zili!!! > On Jun 30, 2022, at 6:21 PM, tison wrote: > > Hello, > > This is the vote for Apache Curator version 5.3.0 > > *** Please download, test and

Re: [VOTE] Release Apache Curator version 5.3.0

t;> >> BTW, I may not have opportunity to attend an offline Apache meetup in this >> month, which seems the only approach to join the WoT. >> >> Best, >> tison. >> >> >> Jordan Zimmerman 于2022年7月1日周五 17:53写道： >> >>> Hi, >>

Re: [VOTE] Release Apache Curator version 5.3.0

Hi, Zili - your PGP key isn't in the WOT. That should be done before I make my vote. Apache has docs on this here: https://infra.apache.org/release-signing.html#web-of-trust i.e. when I verify the hashes I get: gpg: Signature made

Re: RFR CURATOR-640 & Cutting a new release

Hi Tison, I haven't followed this issue and don't have context for it (also I have very little time for Curator these days). Enrico can you help here? -Jordan > On Jun 15, 2022, at 10:17 AM, tison wrote: > > Bubble up this thread for one last time. > > Best, > tison. > > > tison

Re: Too many releases in the dist area ?

Hi, Yeah - that sounds right. I used to delete old releases. I think we only need to keep the current and possibly the previous. > On Mar 17, 2022, at 4:32 PM, Enrico Olivelli wrote: > > Hello, > We have too many releases in the dist area. > ASF policy says that we should keep only one

Re: [VOTE] Release Apache Curator version 5.2.1

Hashes and signatures match, all tests passed on Java 11 +1 Binding -Jordan > On Mar 14, 2022, at 8:20 AM, Enrico Olivelli wrote: > > Hello, > > This is the vote for Apache Curator version 5.2.1 > > *** Please download, test and vote within approx. 72 hours > > Note that we are voting upon

Re: Trying to get a new release out, but tests are failing

No, I haven't noticed this. > On Mar 10, 2022, at 9:19 AM, Enrico Olivelli wrote: > > Hello, > I was going to prepare a new RC, but this test (see belor) is failing > on my laptop. > > Does anyone see all the tests passing ? > We see tests passing on CI for every PR > > Enrico > > [ERROR]

Re: Apache Jira permission request

Unfortunately, we can only assign to committers as far as I know. I'm unable to assign it to you. -Jordan > On Mar 2, 2022, at 1:42 PM, Dora Horvath > wrote: > > Hi! > > I am not sure if my first mail went through so I here it is again. > > I would like to work on a couple of tasks

Re: Release plans?

I don't have the bandwidth currently unfortunately. -Jordan > On Feb 7, 2022, at 7:31 PM, Enrico Olivelli wrote: > > Nathan, > > Il Lun 7 Feb 2022, 18:29 Nathan Gough > ha scritto: > >> Hi there, >> >> I was curious to know when the next planned release (5.2.1

[jira] [Commented] (CURATOR-624) Migrate CI from Travis to GitHub actions

[ https://issues.apache.org/jira/browse/CURATOR-624?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17459895#comment-17459895 ] Jordan Zimmerman commented on CURATOR-624: -- Let's move to Github Actions. I can do it when I

Re: Upgrading ZooKeeper dependency and cutting a release

Sounds good - it's been a long time. Should we merge https://github.com/apache/curator/pull/401 ? > On Dec 14, 2021, at 11:00 AM, Enrico Olivelli wrote: > > Hello, > What about cutting a new release ? > > I would like to commit the ZK dependency

[jira] [Assigned] (CURATOR-535) TestServer random port selection has a race condition

[ https://issues.apache.org/jira/browse/CURATOR-535?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jordan Zimmerman reassigned CURATOR-535: Assignee: (was: Jordan Zimmerman) > TestServer random port selection

[jira] [Commented] (CURATOR-535) TestServer random port selection has a race condition

[ https://issues.apache.org/jira/browse/CURATOR-535?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17453868#comment-17453868 ] Jordan Zimmerman commented on CURATOR-535: -- Please go ahead > TestServer random port select

[jira] [Commented] (CURATOR-622) Add Randomness to LeaderLatch Elections

[ https://issues.apache.org/jira/browse/CURATOR-622?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17443454#comment-17443454 ] Jordan Zimmerman commented on CURATOR-622: -- [~cammckenzie] OK - I think the way previous nodes

[jira] [Commented] (CURATOR-623) DistributedQueue stops filling after long disconnect from cluster

[ https://issues.apache.org/jira/browse/CURATOR-623?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17443336#comment-17443336 ] Jordan Zimmerman commented on CURATOR-623: -- cc [~eolivelli] and [~cammckenzie] for releasing

[jira] [Comment Edited] (CURATOR-623) DistributedQueue stops filling after long disconnect from cluster

[ https://issues.apache.org/jira/browse/CURATOR-623?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17443282#comment-17443282 ] Jordan Zimmerman edited comment on CURATOR-623 at 11/14/21, 10:13 AM

[jira] [Commented] (CURATOR-623) DistributedQueue stops filling after long disconnect from cluster

[ https://issues.apache.org/jira/browse/CURATOR-623?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17443282#comment-17443282 ] Jordan Zimmerman commented on CURATOR-623: -- The test is faulty. There's no guarantee which

[jira] [Comment Edited] (CURATOR-622) Add Randomness to LeaderLatch Elections

[ https://issues.apache.org/jira/browse/CURATOR-622?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17443262#comment-17443262 ] Jordan Zimmerman edited comment on CURATOR-622 at 11/14/21, 8:53 AM

[jira] [Comment Edited] (CURATOR-622) Add Randomness to LeaderLatch Elections

[ https://issues.apache.org/jira/browse/CURATOR-622?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17443262#comment-17443262 ] Jordan Zimmerman edited comment on CURATOR-622 at 11/14/21, 8:53 AM

[jira] [Comment Edited] (CURATOR-622) Add Randomness to LeaderLatch Elections

[ https://issues.apache.org/jira/browse/CURATOR-622?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17443262#comment-17443262 ] Jordan Zimmerman edited comment on CURATOR-622 at 11/14/21, 8:52 AM

[jira] [Commented] (CURATOR-622) Add Randomness to LeaderLatch Elections

[ https://issues.apache.org/jira/browse/CURATOR-622?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17443262#comment-17443262 ] Jordan Zimmerman commented on CURATOR-622: -- > There is no reason to believe that the instan

[jira] [Commented] (CURATOR-622) Add Randomness to LeaderLatch Elections

[ https://issues.apache.org/jira/browse/CURATOR-622?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17443217#comment-17443217 ] Jordan Zimmerman commented on CURATOR-622: -- It would help if you explained why this is better

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

[jira] [Commented] (CURATOR-614) curator5.2 support zookeeper watch recursion ??

[ https://issues.apache.org/jira/browse/CURATOR-614?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17409474#comment-17409474 ] Jordan Zimmerman commented on CURATOR-614: -- [~startjava] can you please find someone who speaks

[jira] [Commented] (CURATOR-613) please implement setAcl Command -R option !!!

[ https://issues.apache.org/jira/browse/CURATOR-613?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17409473#comment-17409473 ] Jordan Zimmerman commented on CURATOR-613: -- [~startjava] can you please find someone who speaks

[jira] [Resolved] (CURATOR-608) ZPath resolved state documentation improvements

[ https://issues.apache.org/jira/browse/CURATOR-608?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jordan Zimmerman resolved CURATOR-608. -- Resolution: Fixed Documentation changed to reflect intended behavior. > ZP

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 the

Re: Write-though API for CuratorCache (is read-my-writes semantics possible) ?

All Curator caches have had that problem. I guess what's needed is a way to listen for writes so that the cache can subscribe. Or, add some kind of write semantics to the CuratorCache API? -Jordan > On Jul 27, 2021, at 7:27 AM, Enrico Olivelli wrote: > > Hello folks, > I was discussing with

Re: [VOTE] Release Apache Curator version 5.2.0

e now. > cheers > > On Mon, Jul 26, 2021 at 3:52 PM Enrico Olivelli <mailto:eolive...@gmail.com>> wrote: > +1 (binding) > > I have run the tests (Ubuntu + jdk8) and verified the signatures. > > I will take care of creating an issue for the license check and enabling

Re: [VOTE] Release Apache Curator version 5.2.0

[ > 53.625 s] > [INFO] Curator Async .. SUCCESS [02:17 > min] > [INFO] Curator Examples ... SUCCESS [ > 2.158 s] > [INFO] Curator Service Discovery Server ... SUCCESS [ > 8.573 s] > [INFO] curato

Re: [VOTE] Release Apache Curator version 5.2.0

Hashes and signature match. My only concern is the TestReconfiguration issue but they pass when run separately. If others are concerned about this I can change my vote. +1 (binding) -Jordan > On Jul 19, 2021, at 11:18 PM, Cameron McKenzie wrote: > > Hello, > > This is the vote for Apache

Re: [VOTE] Release Apache Curator version 5.2.0

Yeah - if I run separately they pass (I just tried it). I'm not sure if that's a concern or not. -JZ > On Jul 21, 2021, at 11:29 PM, Cameron McKenzie wrote: > > I just reran them locally on my machine and they all ran fine. > > On Wed, Jul 21, 2021 at 9:25 PM Jordan Zim

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: Double Locking Issue

A few things... SUSPENDED in Curator means only that the connect has been lost, not that the session has ended. LOST is the state that means the session has ended Be aware of how GCs can affect Curator. See the Tech Note here: https://cwiki.apache.org/confluence/display/CURATOR/TN10

Re: Git website ?

I saw that message on INFRA - at the top it says: "TL;DR: if your project web site is kept in subversion, disregard this email please. If your project web site is using git, and you have not deployed it via .asf.yaml, you MUST switch before July 1st or risk your web site goes stale." Curator's

Re: Cutting a release ?

I too am swamped but I can help out a bit if needed. -Jordan > On May 15, 2021, at 12:15 AM, Cameron McKenzie wrote: > > Sounds good Enrico, > I'm flat out at the moment and changing jobs so I'm not going to be able to > offer much support for the next month or so, but will be able to verify

[jira] [Commented] (CURATOR-595) InterProcessSemaphoreV2 LOST isn't releasing permits for other clients

[ https://issues.apache.org/jira/browse/CURATOR-595?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17330212#comment-17330212 ] Jordan Zimmerman commented on CURATOR-595: -- Are you seeing this in Production? This may

[jira] [Commented] (CURATOR-595) InterProcessSemaphoreV2 LOST isn't releasing permits for other clients

[ https://issues.apache.org/jira/browse/CURATOR-595?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17330211#comment-17330211 ] Jordan Zimmerman commented on CURATOR-595: -- Man - there are a ton of "ephemeral not de

[jira] [Commented] (CURATOR-595) InterProcessSemaphoreV2 LOST isn't releasing permits for other clients

[ https://issues.apache.org/jira/browse/CURATOR-595?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17330182#comment-17330182 ] Jordan Zimmerman commented on CURATOR-595: -- I think the {{acquire(0, ...)}} is the problem

[jira] [Reopened] (CURATOR-595) InterProcessSemaphoreV2 LOST isn't releasing permits for other clients

[ https://issues.apache.org/jira/browse/CURATOR-595?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jordan Zimmerman reopened CURATOR-595: -- Assignee: Jordan Zimmerman BTW - it's intermittent for me too but I'm not convinced

[jira] [Commented] (CURATOR-595) InterProcessSemaphoreV2 LOST isn't releasing permits for other clients

[ https://issues.apache.org/jira/browse/CURATOR-595?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17330125#comment-17330125 ] Jordan Zimmerman commented on CURATOR-595: -- Then try with {{*3}} or {{*4}}. The deletion

Re: NodeCache on ZK lost

t; https://issues.apache.org/jira/browse/FLINK-18677?focusedCommentId=17168001=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-17168001 > > > Jordan Zimmerman 于2021年4月20日周二 上午1:49写道： > >> Once the connection is repaired NodeCache is supposed to

Re: NodeCache on ZK lost

Once the connection is repaired NodeCache is supposed to reconnect. You can see the code here: https://github.com/apache/curator/blob/master/curator-recipes/src/main/java/org/apache/curator/framework/recipes/cache/NodeCache.java#L75

[jira] [Commented] (CURATOR-587) Use ZooKeeper 3.7+ ZooKeeperServerEmbedded in order to start TestingServer

[ https://issues.apache.org/jira/browse/CURATOR-587?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17268630#comment-17268630 ] Jordan Zimmerman commented on CURATOR-587: -- Sounds good to me if it can be done. That embedded

[jira] [Commented] (CURATOR-526) Error logged for valid config - "Invalid config event received: {properties}"

[ https://issues.apache.org/jira/browse/CURATOR-526?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17261703#comment-17261703 ] Jordan Zimmerman commented on CURATOR-526: -- :D I'm very proud of my years at Netflix. I'm glad

[jira] [Commented] (CURATOR-526) Error logged for valid config - "Invalid config event received: {properties}"

[ https://issues.apache.org/jira/browse/CURATOR-526?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17261303#comment-17261303 ] Jordan Zimmerman commented on CURATOR-526: -- bq. Sadly in our case we run ZooKeeper via

Re: State of the project - 2020

uld try to find a way to get more feedback from our users > as already said in this thread, ZooKeeper is very stable and Curator > follows this line, > this is why we do not have much activity on the ML. > > Enrico > > Il giorno mer 25 nov 2020 alle ore 00:58 Jordan

Re: State of the project - 2020

> Probably we should try to find a way to get more feedback from our users > as already said in this thread, ZooKeeper is very stable and Curator > follows this line, > this is why we do not have much activity on the ML. I've tried lots of different ways - SO, Twitter, etc. Nothing seems to work.

Re: State of the project - 2020

y project to release stress. > (I should do more. ;-)) > > On Tue, Nov 24, 2020 at 10:05 PM Cameron McKenzie > wrote: > >> Agreed with all your points Jordan, >> While my employer is still using Curator, I'm no longer actively involved >> in the project. >> cheers >

Re: State of the project - 2020

> 1) Mailing lists Not much activity. There used to be more questions/comments. I've sent several emails with questions/ideas in the past year that have gotten no response at all other than from other committers. > 2) Recent activity from committers We have a good group of committers. But,

[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: JIRA permissions

I guess the Apache perms don't allow non-project members to be assignees. No worries, it's not important. -Jordan > On Aug 12, 2020, at 5:39 AM, Tamas Penzes wrote: > > Hi All, > > I've created a ticket (CURATOR-582 > ) and wanted to assign

Re: jUnit5 migration

Back when Curator was started, TestNG had many more features. If I were to start from scratch today I'd use JUnit 5. But, I don't see much benefit in changing now though I'm not opposed to it. -JZ > On Aug 9, 2020, at 12:42 AM, Enrico Olivelli wrote: > > Tamas > > Il Sab 8 Ago 2020, 21:40

[jira] [Commented] (CURATOR-581) Possible malformed OSGi export pattern

[ https://issues.apache.org/jira/browse/CURATOR-581?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17173533#comment-17173533 ] Jordan Zimmerman commented on CURATOR-581: -- I know nothing of OSGI either maybe we can ask

[jira] [Closed] (CURATOR-580) *** plug

[ https://issues.apache.org/jira/browse/CURATOR-580?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jordan Zimmerman closed CURATOR-580. Resolution: Abandoned > *** plug > > > Key:

[jira] [Updated] (CURATOR-580) *** plug

[ https://issues.apache.org/jira/browse/CURATOR-580?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jordan Zimmerman updated CURATOR-580: - Description: My first toy was [wearing a *** plug all day], and it fits perfectly

[jira] [Reopened] (CURATOR-579) best mulching blades

[ https://issues.apache.org/jira/browse/CURATOR-579?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jordan Zimmerman reopened CURATOR-579: -- > best mulching blades > > > Key:

[jira] [Closed] (CURATOR-579) best mulching blades

[ https://issues.apache.org/jira/browse/CURATOR-579?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jordan Zimmerman closed CURATOR-579. Resolution: Abandoned > best mulching bla

[jira] [Closed] (CURATOR-579) best mulching blades

[ https://issues.apache.org/jira/browse/CURATOR-579?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jordan Zimmerman closed CURATOR-579. Resolution: Abandoned Spam > best mulching bla

[jira] [Commented] (CURATOR-577) WebSite should not like to Confluence for downloads

[ https://issues.apache.org/jira/browse/CURATOR-577?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17155487#comment-17155487 ] Jordan Zimmerman commented on CURATOR-577: -- Note: I've updated the wiki. Please review: https

Re: Returned post for annou...@apache.org

; the ASF mirror system." > > > Enrico > > Il giorno gio 9 lug 2020 alle ore 15:32 Jordan Zimmerman < > jor...@jordanzimmerman.com> ha scritto: > >>> we have to move to the website the full page >> >> Did Sebb say this? I went through this with him la

Re: Returned post for annou...@apache.org

> we have to move to the website the full page Did Sebb say this? I went through this with him last year. I thought our Wiki page was sufficient. I notice the PGP and SHA links are incorrect (old version). Could that be the problem? -Jordan > On Jul 9, 2020, at 8:04 AM, Enrico Olivelli

Re: [RESULT] [VOTE] Release Apache Curator version 5.1.0

Thank you, Enrico, for managing this release. -Jordan > On Jul 3, 2020, at 7:19 AM, Enrico Olivelli wrote: > > Hello, > > The vote to release Curator 5.1.0 has passed. > > +1 (binding): > Cameron McKenzie > Jordan Zimmerman > Shay Shimony > Enrico Olivelli

Re: [VOTE] Release Apache Curator version 5.1.0

I see that on Travis sometimes. It would be nice to get to the bottom of that. -JZ > On Jun 30, 2020, at 8:45 PM, Cameron McKenzie wrote: > > I had to run the tests twice as the TestLeaderLatch got stuck in some sort > of infinite loop.

Re: [VOTE] Release Apache Curator version 5.1.0

- Hash matches - Signature verifies - Tests pass +1 Binding On Tue, Jun 30, 2020 at 8:18 AM Enrico Olivelli wrote: > Hello, > > This is the vote for Apache Curator version 5.1.0 > > *** Please download, test and vote within approx. 72 hours > > Note that we are voting upon the source

[jira] [Commented] (CURATOR-576) Import merge script from ZooKeeper project

[ https://issues.apache.org/jira/browse/CURATOR-576?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17145979#comment-17145979 ] Jordan Zimmerman commented on CURATOR-576: -- Does this need to be in the project/repo? Instead

Re: Cutting 5.1 ?

we are only cutting release from > master, is it expected ? > > > Enrico > > > Il giorno gio 25 giu 2020 alle ore 15:15 Jordan Zimmerman < > jor...@jordanzimmerman.com> ha scritto: > >> Yes - let's do a release. Enrico, we have instructions here: >

Re: Cutting 5.1 ?

ason to hold up 5.1 for this issue. >> Cheers >> >> On Wed, Jun 24, 2020, 5:03 PM Enrico Olivelli wrote: >> >>> @Jordan Zimmerman I have looked again into >>> https://issues.apache.org/jira/browse/ZOOKEEPER-3803 >>> It is an issue to be resolved o

[jira] [Updated] (CURATOR-575) TestingServer shut down can cause NullPointerException

[ https://issues.apache.org/jira/browse/CURATOR-575?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jordan Zimmerman updated CURATOR-575: - Description: There is a race in TestingServer that is identified in ZOOKEEPER-3803

[jira] [Created] (CURATOR-575) TestingServer shut down can cause NullPointerException

Jordan Zimmerman created CURATOR-575: Summary: TestingServer shut down can cause NullPointerException Key: CURATOR-575 URL: https://issues.apache.org/jira/browse/CURATOR-575 Project: Apache

[jira] [Commented] (CURATOR-574) DiscoveryService fatal error on deserializing an empty byte[] as JSON

[ https://issues.apache.org/jira/browse/CURATOR-574?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17142958#comment-17142958 ] Jordan Zimmerman commented on CURATOR-574: -- done > DiscoveryService fatal er

[jira] [Assigned] (CURATOR-574) DiscoveryService fatal error on deserializing an empty byte[] as JSON

[ https://issues.apache.org/jira/browse/CURATOR-574?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jordan Zimmerman reassigned CURATOR-574: Assignee: Enrico Olivelli > DiscoveryService fatal error on deserializ

Re: Cutting 5.1 ?

I'll have a look at ZOOKEEPER-3803 > On Jun 23, 2020, at 6:34 AM, Enrico Olivelli wrote: > > Hi guys, > with 5.0 we introduced a nasty regression and I have committed a fix. > > https://issues.apache.org/jira/issues/?jql=project%20%3D%20CURATOR%20AND%20fixVersion%20%3D%205.1.0 > > It looks

Re: Current master is still 5.0.0-SNAPSHOT

Cameron - maybe you didn't push "master" during the release? I thought that release:perform did that for us but maybe there was an issue? Anyway, please push master and also make sure you do a "git push --tags" > On Jun 15, 2020, at 12:56 AM, Enrico Olivelli wrote: > > Hey folks, > I am

New Committer: Enrico Olivelli

The Project Management Committee (PMC) for Apache Curator has invited Enrico Olivelli to become a committer and PMC member. We are pleased to announce that he has accepted. Being a committer enables easier contribution to the project since there is no need to go via the patch submission process.

[jira] [Commented] (CURATOR-570) Excessive calls to ZooKeeper.updateServerList (which can result in session death)

[ https://issues.apache.org/jira/browse/CURATOR-570?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17129507#comment-17129507 ] Jordan Zimmerman commented on CURATOR-570: -- Oh? It could be then. Sorry if I'm adding noise

[jira] [Commented] (CURATOR-570) Excessive calls to ZooKeeper.updateServerList (which can result in session death)

[ https://issues.apache.org/jira/browse/CURATOR-570?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17129418#comment-17129418 ] Jordan Zimmerman commented on CURATOR-570: -- > ZooKeeper does not give Curator a connect

[jira] [Comment Edited] (CURATOR-570) Excessive calls to ZooKeeper.updateServerList (which can result in session death)

[ https://issues.apache.org/jira/browse/CURATOR-570?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17129364#comment-17129364 ] Jordan Zimmerman edited comment on CURATOR-570 at 6/9/20, 2:55 PM

[jira] [Commented] (CURATOR-570) Excessive calls to ZooKeeper.updateServerList (which can result in session death)

[ https://issues.apache.org/jira/browse/CURATOR-570?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17129364#comment-17129364 ] Jordan Zimmerman commented on CURATOR-570: -- ZooKeeper has an abstraction for this now

[jira] [Comment Edited] (CURATOR-573) No leader is getting selected intermittently

[ https://issues.apache.org/jira/browse/CURATOR-573?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17127399#comment-17127399 ] Jordan Zimmerman edited comment on CURATOR-573 at 6/6/20, 4:34 PM

[jira] [Resolved] (CURATOR-573) No leader is getting selected intermittently

[ https://issues.apache.org/jira/browse/CURATOR-573?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jordan Zimmerman resolved CURATOR-573. -- Resolution: Not A Problem I'm not sure how the clarification helps

[jira] [Resolved] (CURATOR-573) No leader is getting selected intermittently

[ https://issues.apache.org/jira/browse/CURATOR-573?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jordan Zimmerman resolved CURATOR-573. -- Resolution: Not A Problem You are swallowing the interrupted exception. When you get

[jira] [Commented] (CURATOR-573) No leader is getting selected intermittently

[ https://issues.apache.org/jira/browse/CURATOR-573?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17126375#comment-17126375 ] Jordan Zimmerman commented on CURATOR-573: -- You can see in the exception

[jira] [Commented] (CURATOR-573) No leader is getting selected intermittently

[ https://issues.apache.org/jira/browse/CURATOR-573?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17126236#comment-17126236 ] Jordan Zimmerman commented on CURATOR-573: -- It would help if you can build a test case to show

[jira] [Commented] (CURATOR-570) Excessive calls to ZooKeeper.updateServerList (which can result in session death)

[ https://issues.apache.org/jira/browse/CURATOR-570?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17125406#comment-17125406 ] Jordan Zimmerman commented on CURATOR-570: -- I'd like to see this all addressed. So, yeah, let's

  1   2   3   4   5   6   7   8   9   10   >