Mailing-List: contact dev-help@curator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@curator.apache.org
Date: Tue, 21 Apr 2015 16:21:59 +0000 (UTC)
From: "Jordan Zimmerman (JIRA)" <jira@apache.org>
To: dev@curator.apache.org
Message-ID: <JIRA.12780334.1425843630000.63268.1429633319695@Atlassian.JIRA>
In-Reply-To: <JIRA.12780334.1425843630000@Atlassian.JIRA>
References: <JIRA.12780334.1425843630000@Atlassian.JIRA>
 <JIRA.12780334.1425843630250@arcas>
Subject: [jira] [Commented] (CURATOR-192) ChildReaper loggs error when the
 path to reap children from is empty
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/CURATOR-192?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14505209#comment-14505209 ] 

Jordan Zimmerman commented on CURATOR-192:
------------------------------------------

NoNode would only be thrown if the _parent_ node didn't exist. This means a node was added to the ChildReaper that no longer exists. Shouldn't this be logged?

> ChildReaper loggs error when the path to reap children from is empty
> --------------------------------------------------------------------
>
>                 Key: CURATOR-192
>                 URL: https://issues.apache.org/jira/browse/CURATOR-192
>             Project: Apache Curator
>          Issue Type: Bug
>          Components: Recipes
>    Affects Versions: 2.7.1
>            Reporter: Ricardo Ferreira
>            Priority: Minor
>
> When retrieving the children to reap, if there are no children a KeeperErrorCode = NoNode is thrown.
> This exception is logged as an error.
> This should be an expected behavior, so either a KeeperException.NoNodeException should be caught and silenced or logged as debug/trace.


--
This message was sent by Atlassian JIRA
(v6.3.4#6332)