[
https://issues.apache.org/jira/browse/CURATOR-90?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13911654#comment-13911654
]
Jordan Zimmerman commented on CURATOR-90:
-----------------------------------------
With this patch, you get all-or-nothing suppressing of the event. I think
that's a problem. Ideally, the first event would be logged and subsequent
events would be suppressed or logged as debug. This is more involved, of course.
> 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)
