[
https://issues.apache.org/jira/browse/NIFI-3731?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16106632#comment-16106632
]
Wesley L Lawrence commented on NIFI-3731:
-----------------------------------------
Might be something in Apache Curator, not NiFi itself.
https://issues.apache.org/jira/browse/CURATOR-272
I've seen these messages spam as well when ZK goes down, or gets into a state
where it can't be connected to.
> Excessive Curator messages
> --------------------------
>
> Key: NIFI-3731
> URL: https://issues.apache.org/jira/browse/NIFI-3731
> Project: Apache NiFi
> Issue Type: Bug
> Components: Core Framework
> Affects Versions: 1.1.1
> Reporter: Mark Bean
> Priority: Minor
>
> Occasionally, while testing scenarios on a 3-Node cluster a Node will be
> removed from the cluster. Sometimes, the log files begin filling with an
> inordinate amount of repeated messages from the Curator. I'm still trying to
> track down what instigates this, but most likely it is when one of the 3 ZK
> servers becomes unavailable. Is there a way to suppress or reduce the
> frequency of the following messages? Currently, it is repeated more than
> once/millisecond.
> 2017-04-19 16:25:09,824 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(CuratorFramworkImpl.java:838)
> [curator-framework-2.11.0.jar:na]
> at
> org.apache.curator.framework.imps.CuratorFrameworkImpl.backgroundOperationsLoop(CuratorFrameworkImpl.java:809)
> [curator-framework-2.11.0.jar:na]
> at
> org.apache.curator.framework.imps.CuratorFrameworkImpl.access$300(CuratorFrameworkImpl.java:64)
> [curator-framework-2.11.0.jar:na]
> at
> org.apache.curator.framework.imps.CuratorFrameworkImpl.$4.call(CuratorFrameworkImpl.java:267)
> [curator-framework-2.11.0.jar:na]
> at java.util.concurrent.FutureTask.run(FutureTask.java:266)
> [na:1.8.0_121]
> at
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180)
> [na:1.8.0_121]
> at
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293)
> [na:1.8.0_121]
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
> [na:1.8.0_121]
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> [na:1.8.0_121]
> at java.lang.Thread.run(Thread.java:745) [na:1.8.0_121]
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
