[
https://issues.apache.org/jira/browse/NIFI-6875?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17047889#comment-17047889
]
Wyllys Ingersoll edited comment on NIFI-6875 at 2/28/20 7:09 PM:
-----------------------------------------------------------------
Seeing very similar issue with nifi 1.11.3 and a zookeeper cluster running zk
3.4.10. The same zookeeper cluster manages a nifi 1.9.2 cluster just fine, but
when i try to upgrade to 1.11.3, it never works, just repeats the following
over and over:
{noformat}
2020-02-28 13:58:43,195 INFO [main-EventThread]
o.a.c.f.state.ConnectionStateManager State change: RECONNECTED
2020-02-28 13:58:43,195 INFO [Curator-ConnectionStateManager-0]
o.a.n.c.l.e.CuratorLeaderElectionManager
org.apache.nifi.controller.leader.election.CuratorLeaderElectionManager$ElectionListener@54434790
Connection State changed to RECONNECTED
2020-02-28 13:58:43,296 INFO [main-EventThread]
o.a.c.f.state.ConnectionStateManager State change: SUSPENDED
2020-02-28 13:58:43,296 WARN [main] o.a.nifi.controller.StandardFlowService
There is currently no Cluster Coordinator. This often happens upon restart of
NiFi when running an embedded ZooKeeper. Will register this node to become the
active Cluster Coordinator and will attempt to connect to cluster again
2020-02-28 13:58:43,297 INFO [main] o.a.n.c.l.e.CuratorLeaderElectionManager
CuratorLeaderElectionManager[stopped=false] Attempted to register Leader
Election for role 'Cluster Coordinator' but this role is already registered
2020-02-28 13:58:43,297 INFO [Curator-ConnectionStateManager-0]
o.a.n.c.l.e.CuratorLeaderElectionManager
org.apache.nifi.controller.leader.election.CuratorLeaderElectionManager$ElectionListener@54434790
Connection State changed to SUSPENDED
2020-02-28 13:58:43,757 INFO [main-EventThread]
o.a.c.f.state.ConnectionStateManager State change: RECONNECTED
2020-02-28 13:58:43,757 INFO [Curator-ConnectionStateManager-0]
o.a.n.c.l.e.CuratorLeaderElectionManager
org.apache.nifi.controller.leader.election.CuratorLeaderElectionManager$ElectionListener@54434790
Connection State changed to RECONNECTED
2020-02-28 13:58:43,859 INFO [main-EventThread]
o.a.c.f.state.ConnectionStateManager State change: SUSPENDED
2020-02-28 13:58:43,859 INFO [Curator-ConnectionStateManager-0]
o.a.n.c.l.e.CuratorLeaderElectionManager
org.apache.nifi.controller.leader.election.CuratorLeaderElectionManager$ElectionListener@54434790
Connection State changed to SUSPENDED
2020-02-28 13:58:43,859 ERROR [main-EventThread]
o.a.c.f.imps.CuratorFrameworkImpl Background operation retry gave up
org.apache.zookeeper.KeeperException$ConnectionLossException: KeeperErrorCode =
ConnectionLoss
at org.apache.zookeeper.KeeperException.create(KeeperException.java:102)
at
org.apache.curator.framework.imps.CuratorFrameworkImpl.checkBackgroundRetry(CuratorFrameworkImpl.java:862)
at
org.apache.curator.framework.imps.CuratorFrameworkImpl.processBackgroundOperation(CuratorFrameworkImpl.java:647)
at
org.apache.curator.framework.imps.WatcherRemovalFacade.processBackgroundOperation(WatcherRemovalFacade.java:152)
at
org.apache.curator.framework.imps.GetConfigBuilderImpl$2.processResult(GetConfigBuilderImpl.java:222)
at
org.apache.zookeeper.ClientCnxn$EventThread.processEvent(ClientCnxn.java:601)
at org.apache.zookeeper.ClientCnxn$EventThread.run(ClientCnxn.java:510)
{noformat}
was (Author: wyllys):
Seeing very similar issue with nifi 1.11.3 and a zookeeper cluster running zk
3.4.10
> Nifi Zookeeper Cluster_Mode broken in 1.10.0
> --------------------------------------------
>
> Key: NIFI-6875
> URL: https://issues.apache.org/jira/browse/NIFI-6875
> Project: Apache NiFi
> Issue Type: Bug
> Components: Core Framework, Flow Versioning
> Affects Versions: 1.10.0
> Environment: Kubernetes, Linux
> Reporter: Glenn Wolfe
> Priority: Blocker
> Labels: bug, cluster-mode, kubernetes
>
> Expected: Exact same configuration and setup works perfectly on prior version
> (1.9.2), as soon as I upgrade version, NIfi is unable to initialize.
>
> With external zookeeper (cluster_mode) configuration, Nifi is unable to
> successfully elect leader and stuck in 'Invalid State: The Flow Controller is
> initializing the Data Flow'.
>
> Logs: (Stuck in Loop)
> ```
> 2019-11-15 17:00:05,991 INFO [main-EventThread]
> o.a.c.f.state.ConnectionStateManager State change: RECONNECTED
> 2019-11-15 17:00:05,991 INFO [Curator-ConnectionStateManager-0]
> o.a.n.c.l.e.CuratorLeaderElectionManager
> org.apache.nifi.controller.leader.election.CuratorLeaderElectionManager$ElectionListener@256c961a
> Connection State changed to RECONNECTED
> 2019-11-15 17:00:06,092 INFO [main-EventThread]
> o.a.c.f.state.ConnectionStateManager State change: SUSPENDED
> 2019-11-15 17:00:06,092 WARN [main] o.a.nifi.controller.StandardFlowService
> There is currently no Cluster Coordinator. This often happens upon restart of
> NiFi when running an embedded ZooKeeper. Will register this node to become
> the active Cluster Coordinator and will attempt to connect to cluster again
> 2019-11-15 17:00:06,093 INFO [main] o.a.n.c.l.e.CuratorLeaderElectionManager
> CuratorLeaderElectionManager[stopped=false] Attempted to register Leader
> Election for role 'Cluster Coordinator' but this role is already registered
> ```
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
