Mike Drob created CURATOR-313:
---------------------------------
Summary: Verify that Curator logging is appropriate
Key: CURATOR-313
URL: https://issues.apache.org/jira/browse/CURATOR-313
Project: Apache Curator
Issue Type: Bug
Components: Framework
Affects Versions: 2.7.1
Reporter: Mike Drob
Assignee: Mike Drob
>From a customer:
{quote}
When Curator looses a connection with Zookeeper it does print a rather large
amount of stack traces into the logs. I'm unsure if this log spamming should be
investigated to determine if there is a way of rate limiting the messages, or
move the stack trace to DEBUG and have a simple 1 liner stating Zookeeper is
unavailable in WARN.
{quote}
This might have already been taken care of in newer version, so this is at
least 50% a reminder to myself to investigate it more thoroughly.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
