You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@curator.apache.org by "Evaristo (JIRA)" <ji...@apache.org> on 2014/05/02 17:14:16 UTC
[jira] [Updated] (CURATOR-90) Reduce the verbosity of connection
error log messages
[ https://issues.apache.org/jira/browse/CURATOR-90?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Evaristo updated CURATOR-90:
----------------------------
Attachment: curator-90-evaristo.patch
I attach a potential patch, It prints the first ocurrence of ConnectionLossException or CuratorConnectionLossException and the next exceptions are logged as debug.
Comments welcome
> 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, curator-90-evaristo.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.2#6252)