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 26C29200D70 for ; Fri, 22 Dec 2017 06:23:10 +0100 (CET) Received: by cust-asf.ponee.io (Postfix) id 258E6160C2C; Fri, 22 Dec 2017 05:23:10 +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 6AC39160C2D for ; Fri, 22 Dec 2017 06:23:09 +0100 (CET) Received: (qmail 775 invoked by uid 500); 22 Dec 2017 05:23:08 -0000 Mailing-List: contact dev-help@curator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@curator.apache.org Delivered-To: mailing list dev@curator.apache.org Received: (qmail 553 invoked by uid 99); 22 Dec 2017 05:23:08 -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; Fri, 22 Dec 2017 05:23:08 +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 AFBB11A05A8 for ; Fri, 22 Dec 2017 05:23:07 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd2-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -99.202 X-Spam-Level: X-Spam-Status: No, score=-99.202 tagged_above=-999 required=6.31 tests=[KAM_ASCII_DIVIDERS=0.8, RCVD_IN_DNSWL_NONE=-0.0001, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] autolearn=disabled 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 PhTsvGpdUQuC for ; Fri, 22 Dec 2017 05:23:04 +0000 (UTC) Received: from mailrelay1-us-west.apache.org (mailrelay1-us-west.apache.org [209.188.14.139]) by mx1-lw-us.apache.org (ASF Mail Server at mx1-lw-us.apache.org) with ESMTP id BE8015F39D for ; Fri, 22 Dec 2017 05:23:03 +0000 (UTC) Received: from jira-lw-us.apache.org (unknown [207.244.88.139]) by mailrelay1-us-west.apache.org (ASF Mail Server at mailrelay1-us-west.apache.org) with ESMTP id 3E0A3E0041 for ; Fri, 22 Dec 2017 05:23:03 +0000 (UTC) Received: from jira-lw-us.apache.org (localhost [127.0.0.1]) by jira-lw-us.apache.org (ASF Mail Server at jira-lw-us.apache.org) with ESMTP id 45A9F212F7 for ; Fri, 22 Dec 2017 05:23:01 +0000 (UTC) Date: Fri, 22 Dec 2017 05:23:00 +0000 (UTC) From: "ASF GitHub Bot (JIRA)" To: dev@curator.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (CURATOR-388) PathChildrenCache stops working if container node is auto-removed and later recreated MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 archived-at: Fri, 22 Dec 2017 05:23:10 -0000 [ https://issues.apache.org/jira/browse/CURATOR-388?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16300968#comment-16300968 ] ASF GitHub Bot commented on CURATOR-388: ---------------------------------------- Github user asfgit closed the pull request at: https://github.com/apache/curator/pull/249 > PathChildrenCache stops working if container node is auto-removed and later recreated > ------------------------------------------------------------------------------------- > > Key: CURATOR-388 > URL: https://issues.apache.org/jira/browse/CURATOR-388 > Project: Apache Curator > Issue Type: Bug > Components: Recipes > Affects Versions: 3.2.1 > Environment: zookeeper 3.5.2-alpha > Reporter: Rhys Yarranton > Assignee: Jordan Zimmerman > Fix For: 4.0.1 > > Attachments: EmptyPathChildrenCacheTest.java > > > PathChildrenCache uses EnsureContainers to create the path as a container(if it does not already exist). If at some point that container is empty, ZooKeeper may remove it. If at some later point the path is recreated and a child node added, the PathChildrenCache will not detect it. No event will be fired, nor will the child node appear in getCurrentData(). > The attached test reproduces the problem most of the time if the ZooKeeper server has znode.container.checkIntervalMs reduced to 1000. > A workaround is to explicitly create the path as a non-container before starting the PathChildrenCache. > NB there are two related problems here. One is that it has trouble handling containers. More serious is that it creates a container, thus running itself into trouble. -- This message was sent by Atlassian JIRA (v6.4.14#64029)