You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@nifi.apache.org by "Shawn Weeks (Jira)" <ji...@apache.org> on 2020/01/16 15:56:00 UTC
[jira] [Created] (NIFI-7035) Don't spam logs with Apache Curator
errors on Zookeeper Disconnect
Shawn Weeks created NIFI-7035:
---------------------------------
Summary: Don't spam logs with Apache Curator errors on Zookeeper Disconnect
Key: NIFI-7035
URL: https://issues.apache.org/jira/browse/NIFI-7035
Project: Apache NiFi
Issue Type: Improvement
Reporter: Shawn Weeks
Sometimes when you startup NiFi and not all of the Zookeeper nodes aren't up it fills the logs with Apache Curator errors like this one. We should be able to improve this a bit as logging the same error repeatedly isn't helpful.
{code:java}
2020-01-16 08:58:28,767 ERROR [Curator-Framework-0] o.a.c.f.imps.CuratorFrameworkImpl Background retry gave up
org.apache.curator.CuratorConnectionLossException: KeeperErrorCode = ConnectionLoss
at org.apache.curator.framework.imps.CuratorFrameworkImpl.performBackgroundOperation(CuratorFrameworkImpl.java:972)
at org.apache.curator.framework.imps.CuratorFrameworkImpl.backgroundOperationsLoop(CuratorFrameworkImpl.java:943)
at org.apache.curator.framework.imps.CuratorFrameworkImpl.access$300(CuratorFrameworkImpl.java:66)
at org.apache.curator.framework.imps.CuratorFrameworkImpl$4.call(CuratorFrameworkImpl.java:346)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
at java.lang.Thread.run(Thread.java:748)
{code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)