[
https://issues.apache.org/jira/browse/CURATOR-90?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13988316#comment-13988316
]
ASF GitHub Bot commented on CURATOR-90:
---------------------------------------
GitHub user eceejcr opened a pull request:
https://github.com/apache/curator/pull/6
CURATOR-90
Making Connection erros less verbose. Only first error is logged with error
level; subsequent errors are logged as debug
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/eceejcr/curator CURATOR-90
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/curator/pull/6.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #6
----
commit ab3ff72d309378f3c6e166e47e75b7ba49835f20
Author: eceejcr <[email protected]>
Date: 2014-05-02T21:53:40Z
Making Connection erros less verbose. Only first error is logged with
error level; subsequent errors are logged as debug
----
> 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)
