Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id 39115200C18 for ; Sat, 11 Feb 2017 16:06:08 +0100 (CET) Received: by cust-asf.ponee.io (Postfix) id 2CA13160B51; Sat, 11 Feb 2017 15:06:08 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id 73D4B160B4A for ; Sat, 11 Feb 2017 16:06:07 +0100 (CET) Received: (qmail 88969 invoked by uid 500); 11 Feb 2017 15:06:06 -0000 Mailing-List: contact user-help@zookeeper.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: user@zookeeper.apache.org Delivered-To: mailing list user@zookeeper.apache.org Received: (qmail 88956 invoked by uid 99); 11 Feb 2017 15:06:05 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd2-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 11 Feb 2017 15:06:05 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd2-us-west.apache.org (ASF Mail Server at spamd2-us-west.apache.org) with ESMTP id A77BF1A070C for ; Sat, 11 Feb 2017 15:06:04 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd2-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 1.88 X-Spam-Level: * X-Spam-Status: No, score=1.88 tagged_above=-999 required=6.31 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=2, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=disabled Authentication-Results: spamd2-us-west.apache.org (amavisd-new); dkim=pass (1024-bit key) header.d=tink.se Received: from mx1-lw-us.apache.org ([10.40.0.8]) by localhost (spamd2-us-west.apache.org [10.40.0.9]) (amavisd-new, port 10024) with ESMTP id GWBL_K94zC8w for ; Sat, 11 Feb 2017 15:06:02 +0000 (UTC) Received: from mail-wm0-f43.google.com (mail-wm0-f43.google.com [74.125.82.43]) by mx1-lw-us.apache.org (ASF Mail Server at mx1-lw-us.apache.org) with ESMTPS id 268125F342 for ; Sat, 11 Feb 2017 15:06:02 +0000 (UTC) Received: by mail-wm0-f43.google.com with SMTP id 196so70334549wmm.1 for ; Sat, 11 Feb 2017 07:06:02 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=tink.se; s=tink; h=mime-version:from:date:message-id:subject:to; bh=5yT/5EfDqdngmJ1JvJC5MpydVpG9oQiAwO4DiCWVfg4=; b=RlBoQAkyy+fjUodCfzDMCbjP33X2qGCQYUKdNouFBQoMPDvbV/Z7ysZLvxc+h+/S54 lpNgL6MIuf44jHdPsRfoOPc5mQI/fGGxx3e+MuYYBRlcPT7/7ceCg4hP0yX5us4wNpZO Be/MLZI86dx+4ZH16N9i2rJfUssZvvjdX+8rk= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=5yT/5EfDqdngmJ1JvJC5MpydVpG9oQiAwO4DiCWVfg4=; b=ECQcPN73HeA1frwgYgzUtmrKPrrpvZeeaq7W/N9aGNTAG2+bY8QQHOpto/Fqxt9QR+ lgm4+NoDdXBpTO8MFMRP6/mKQdXjf7HpHFb/v83P7CsRaWedTf715b7iomJmxOVtG1jD KNR/p+aN0SzVII42krzltIROusCiELbdwog2ojtRAqJY2Foaompe+m9RJOVBeiO2ZfSU R0QPa5WAh5omd1KtNw3i/CNn7i0yXQq3GalIFJ6Z8JSJgfXc7EXyx3pRynjZiK1TyXwR Fks1FPHniHSaEQSGuDXckZlEIghW/nBTphTT9GdU1W3ihYmOPwrYvub26oUVeagVJ/0e teJA== X-Gm-Message-State: AMke39luu4B+wOiFwCerY1MHDA2qoFDMls6T5dWbfaBErZopPyTCCRUZbudi/Q563ANlRQ3axHuK7GUBJJLtxtdC X-Received: by 10.28.130.212 with SMTP id e203mr10940195wmd.104.1486825557945; Sat, 11 Feb 2017 07:05:57 -0800 (PST) MIME-Version: 1.0 Received: by 10.28.197.5 with HTTP; Sat, 11 Feb 2017 07:05:37 -0800 (PST) From: Jens Rantil Date: Sat, 11 Feb 2017 16:05:37 +0100 Message-ID: Subject: New 3.5.X release To: "" Content-Type: multipart/alternative; boundary=001a11442c9e3985470548428d66 archived-at: Sat, 11 Feb 2017 15:06:08 -0000 --001a11442c9e3985470548428d66 Content-Type: text/plain; charset=UTF-8 Hello Zoo workers, We started hitting the NPE in [1] which lead to Zookeeper not cleaning up our znodes anymore. We've worked around the issue[2], but it's just a matter time before this happens again. A fix for [1] has been merge into the 1.5.X branch. I asked in the JIRA issue about when a new release with this fix could be out, but has so far not gotten an answer. Is there anyone on this mailing list who could answer this? [1] https://issues.apache.org/jira/browse/ZOOKEEPER-2464 [2] Luckily we don't have any persistent data in our Zookeeper cluster so, bringing it down fully and removing all logs and snapshots fixed things for us. Thanks, Jens -- Jens Rantil Backend engineer Tink AB Email: jens.rantil@tink.se Phone: +46 708 84 18 32 Web: www.tink.se Facebook Linkedin Twitter --001a11442c9e3985470548428d66--