[CURATOR-313] Verify that Curator logging is appropriate

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Not A Problem
• Affects Version/s: 2.7.1
• Component/s: Framework
• Assignee: Unassigned
• Reporter: Mike Drob
• Created: 29/Mar/16 16:57
• Updated: 23/Jul/17 16:55
• Resolved: 23/Jul/17 16:55

Description

From a customer:

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.

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.