Mailing-List: contact dev-help@curator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@curator.apache.org
Date: Tue, 25 Feb 2014 23:21:20 +0000 (UTC)
From: "Jordan Zimmerman (JIRA)" <jira@apache.org>
To: dev@curator.incubator.apache.org
Message-ID: <JIRA.12697043.1393291142032.104756.1393370480235@arcas>
In-Reply-To: <JIRA.12697043.1393291142032@arcas>
References: <JIRA.12697043.1393291142032@arcas>
Subject: [jira] [Commented] (CURATOR-90) Reduce the verbosity of connection
 error log messages
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Jordan Zimmerman commented on CURATOR-90:
-----------------------------------------

That's a tough one. It's not a simple problem. 

> Reduce the verbosity of connection error log messages
> -----------------------------------------------------
>
>                 Key: CURATOR-90
>                 URL: https://issues.apache.org/jira/browse/CURATOR-90
>             Project: Apache Curator
>          Issue Type: Improvement
>          Components: Framework
>    Affects Versions: 2.4.0
>            Reporter: Julio Lopez
>            Priority: Minor
>         Attachments: CURATOR-90.patch
>
>
> On connection error, such as a network disconnection from the ZK cluster,  CuratorFrameworkImpl does excessive logging.  While a system property, namely PROPERTY_DONT_LOG_CONNECTION_ISSUES = "curator-dont-log-connection-problems", can be set to avoid filling out the logs with connection error messages, this is an all or nothing setting.
> It is desirable to allow for less verbose logging that can be more easily controlled and filtered using the logging framework of choice.


--
This message was sent by Atlassian JIRA
(v6.1.5#6160)