From dev-return-81752-archive-asf-public=cust-asf.ponee.io@zookeeper.apache.org Wed Jun 26 09:20:35 2019 Return-Path: X-Original-To: archive-asf-public@cust-asf.ponee.io Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [207.244.88.153]) by mx-eu-01.ponee.io (Postfix) with SMTP id 7BBF018064D for ; Wed, 26 Jun 2019 11:20:35 +0200 (CEST) Received: (qmail 41771 invoked by uid 500); 26 Jun 2019 09:20:34 -0000 Mailing-List: contact dev-help@zookeeper.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@zookeeper.apache.org Delivered-To: mailing list dev@zookeeper.apache.org Received: (qmail 41738 invoked by uid 99); 26 Jun 2019 09:20:33 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd1-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 26 Jun 2019 09:20:33 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd1-us-west.apache.org (ASF Mail Server at spamd1-us-west.apache.org) with ESMTP id BEE93C08F8 for ; Wed, 26 Jun 2019 09:20:32 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd1-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 1.801 X-Spam-Level: * X-Spam-Status: No, score=1.801 tagged_above=-999 required=6.31 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HTML_MESSAGE=2, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=disabled Authentication-Results: spamd1-us-west.apache.org (amavisd-new); dkim=pass (2048-bit key) header.d=cloudera.com Received: from mx1-lw-us.apache.org ([10.40.0.8]) by localhost (spamd1-us-west.apache.org [10.40.0.7]) (amavisd-new, port 10024) with ESMTP id rb5Qt3eH6ofB for ; Wed, 26 Jun 2019 09:20:31 +0000 (UTC) Received: from mail-pl1-f175.google.com (mail-pl1-f175.google.com [209.85.214.175]) by mx1-lw-us.apache.org (ASF Mail Server at mx1-lw-us.apache.org) with ESMTPS id C0D295F19D for ; Wed, 26 Jun 2019 09:20:30 +0000 (UTC) Received: by mail-pl1-f175.google.com with SMTP id c14so1126231plo.0 for ; Wed, 26 Jun 2019 02:20:30 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to; bh=Tm4gUq7VfcBEXzk67YsjsN5f+1GmnNpDWA6plABq15M=; b=LEarnLu9JqL1KQWEljv9Nt2ftWtW146CyywGcyRVYEL3USSr0t2TIrV1cuWdp8+II7 oxADL6AxGBC9pR8jHSB37eYjimBdOGgqcxIQ+XhGBK0ViCg2bOW+AHuQG47jFPk8fZNB UYju57ftDUr8uuUzZyz5R5mLXSfUBgvdmZCLN7rb3NBQbHSZSlds8Tf8NDZNayzwOU2f 7YoI3lTJH2+9mXTTlXsAqtnL+6501dMvWu8aw5085Ar6UQj+kUR6SvVJ/S9TYfs1CsJ3 yh/vYg6rDlvBS1rfPJvvx5DBZyvac63hP+SuEeHPZALTC2uxM/ngMn5VjjaOPVsgYc0y qCWQ== X-Gm-Message-State: APjAAAWui9GfNS8plG7D8g+QoZuH2iH/5rMC6+mITyOmZjZNJREljGPO 6uBlZGeMrab9/QXhHGgRTZ30BhmX0Ot1iw0oQy13lUdKl64= X-Google-Smtp-Source: APXvYqys1hsq2OvNQAduAytrudfiZWcLphYFi+HD7bz/966sXczQr/dG6V7nvdeuv3MD8a1Wqi+cGZPDbs9/3KR2v3A= X-Received: by 2002:a17:902:a504:: with SMTP id s4mr4201382plq.117.1561540829790; Wed, 26 Jun 2019 02:20:29 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: Norbert Kalmar Date: Wed, 26 Jun 2019 11:20:13 +0200 Message-ID: Subject: Re: Time to think about a 3.6.0 release? To: dev@zookeeper.apache.org Content-Type: multipart/alternative; boundary="000000000000766946058c368e5f" --000000000000766946058c368e5f Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Sorry, correction, I just followed up on ZOOKEEPER-2136, patch is not ready, and maybe not even a blocker for 3.6.0? On Wed, Jun 26, 2019 at 11:16 AM Norbert Kalmar wrote: > Hi Fangmin, > > I checked all 3 PRs, looks like they pretty much reviewed, some minor > questions remain. > But we have 302 tickets open where fixVersion is 3.6.0, good news is only > 1 blocker (ZOOKEEPER-2136), which already has a patch. I'll see that this > blocker gets committed. > There is also 9 critical for 3.6.0. > > Regards, > Norbert > > > > On Wed, Jun 26, 2019 at 1:27 AM Fangmin Lv wrote: > >> It's great to have a 3.6.0 release, currently all the FB contributed >> features has been running inside FB for more than a month, so it >> should be stable enough for community to use. >> >> Also I agreed with Patrick's point to review all flags and consider to >> turn >> on by default. >> >> For the pending PRs, the following might be higher priority and would be >> nice to include in the 3.6.0 release: >> >> * ZOOKEEPER-3356: Implement advanced Netty flow control based on feedbac= k >> from ZK to avoid OOM issue >> * ZOOKEEPER-3145: Avoid watch missing issue due to stale pzxid when >> replaying CloseSession txn with fuzzy snapshot >> * ZOOKEEPER-3240: Close socket on Learner shutdown to avoid dangling >> socket >> >> Thanks, >> Fangmin >> >> On Sat, Jun 15, 2019 at 9:21 AM Patrick Hunt wrote: >> >> > Good idea. Agree on including anything we've postponed to a new cycle = - >> the >> > patch from mapr is an obvious one to consider. >> > >> > We should also look at things we've disabled by default and consider >> > whether we can turn them on by default. If not why not, and what can w= e >> do >> > to fix this in a subsequent release. >> > >> > Have we deprecated anything that we should now remove? >> > >> > Also a good time to review the state of Java versions and make changes >> wrt >> > supported versions and so forth. >> > >> > There was a proposal to remove contribs, or at least consider the ones >> that >> > are still valuable vs moving some out. We should do that as well. >> > >> > Regards, >> > >> > Patrick >> > >> > On Sat, Jun 15, 2019 at 9:02 AM Jordan Zimmerman < >> > jordan@jordanzimmerman.com> >> > wrote: >> > >> > > On Persistent/Recursive watches: I=E2=80=99m willing to rebase, etc = if there=E2=80=99s >> > > confidence it will be merged. >> > > >> > > =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D >> > > Jordan Zimmerman >> > > >> > > > On Jun 15, 2019, at 10:59 AM, Andor Molnar >> > > > >> > > wrote: >> > > > >> > > > Hi Enrico! >> > > > >> > > > Very good point, I entirely support the idea. >> > > > >> > > > Question to Friends@Facebook and Twitter contributors: how many >> > > outstanding >> > > > Jiras/PRs do you have which you would like to see in 3.6? >> > > > >> > > > I'd also like to highlight the long outstanding PR from Mapr: >> > > > https://github.com/apache/zookeeper/pull/730 >> > > > >> > > > And some great new features which are still looking for to be >> merged: >> > > > - Persistent recursive watchers: >> > > > https://github.com/apache/zookeeper/pull/136 >> > > > - Enforce client auth: https://github.com/apache/zookeeper/pull/11= 8 >> > > > - Slow operation log >> > > > - Jetty port unification >> > > > >> > > > Regards, >> > > > Andor >> > > > >> > > > >> > > > >> > > > >> > > > >> > > >> On Sat, Jun 15, 2019 at 1:31 PM Enrico Olivelli < >> eolivelli@gmail.com> >> > > wrote: >> > > >> >> > > >> Hi Zookeepers ! >> > > >> I checked on JIRA and it seems that master in good shape, no real >> > > blockers >> > > >> that mine the stability of the code. >> > > >> >> > > >> We have plenty of cool pull requests almost ready to be merged >> (mostly >> > > from >> > > >> Facebook friends and Twitter fork) >> > > >> >> > > >> Current master branch is full of great features in respect to 3.5= . >> > > >> >> > > >> AFAIK There is no incompatibility with 3.5 so it is okay to stay >> with >> > > >> 3.6.0, although I think that there is so much stuff to legit a >> switch >> > to >> > > >> 4.0.0 (but we can reserve such bump for the time we will separate >> the >> > > java >> > > >> client and create a minimal compatibility breakage) >> > > >> >> > > >> Thoughts? >> > > >> >> > > >> Enrico >> > > >> >> > > >> > >> > --000000000000766946058c368e5f--