You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@nifi.apache.org by "Jonathan Johnson (Jira)" <ji...@apache.org> on 2023/10/27 17:01:00 UTC
[jira] [Comment Edited] (NIFI-12232) Frequent "failed to connect node to cluster because local flow controller partially updated. Administrator should disconnect node and review flow for corruption"
[ https://issues.apache.org/jira/browse/NIFI-12232?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17780464#comment-17780464 ]
Jonathan Johnson edited comment on NIFI-12232 at 10/27/23 5:00 PM:
-------------------------------------------------------------------
Hello,
I am also having a number of the "Failed to connect node to cluster..." errors in my system leaving nodes disconnected from the cluster until stopping NiFi and allowing the node to recreate its canvas from the cluster. I am trying to determine if we are experiencing same issues or if this should be its own ticket.
My logs immediately before the "Failed to connect ..." errors look like:
{code:java}
2023-10-27 09:41:08,373 INFO [Heartbeat Monitor Thread-1] o.a.n.c.c.node.NodeClusterCoordinator Status of node1.nifi:9441 changed from NodeConnectionStatus[nodeId=node1.nifi:9441, state=DISCONNECTED, Disconnect Code=Lack of Heartbeat, Disconnect Reason=Have not received a heartbeat from node in 3 seconds, updateId=83] to NodeConnectionStatus[nodeId=node1.nifi:9441, state=CONNECTING, updateId=84]
<REMOVED FOR READABILITY>
2023-10-27 09:41:08,452 INFO [Reconnect to Cluster] o.a.nifi.controller.StandardFlowService Processing reconnection request from cluster coordinator.
<REMOVED FOR READABILITY>
2023-10-27 09:41:08,720 INFO [Reconnect to Cluster] o.a.nifi.groups.StandardProcessGroup Template[id=9cd572fa-2d18-3228-9a10-8f2438ae9459] removed from flow
2023-10-27 09:41:08,722 INFO [Reconnect to Cluster] o.a.n.f.s.StandardVersionedComponentSynchronizer No differences between current flow and proposed flow for StandardProcessGroup[identifier=4e8898ea-018b-1000-14a4-b336fae6590e,name=NiFi Flow]
2023-10-27 09:41:08,724 INFO [Reconnect to Cluster] o.a.nifi.groups.StandardProcessGroup StandardFunnel[id=71590595-018b-1000-ffff-ffff94fe7f50-temp-funnel] added to StandardProcessGroup[identifier=71590595-018b-1000-ffff-ffff94fe7f50,name=testetst]
2023-10-27 09:41:08,731 INFO [Reconnect to Cluster] o.a.n.c.s.AffectedComponentSet Starting the following components: AffectedComponentSet[inputPorts=[], outputPorts=[], remoteInputPorts=[], remoteOutputPorts=[], processors=[], parameterProviders=[], flowRegistryCliens=[], controllerServices=[], reportingTasks=[]]
2023-10-27 09:41:08,731 INFO [Reconnect to Cluster] o.a.nifi.controller.StandardFlowService Disconnecting node due to Failed to properly handle Reconnection request due to org.apache.nifi.controller.serialization.FlowSynchronizationException: Failed to connect node to cluster because local flow controller partially updated. Administrator should disconnect node and review flow for corruption.
2023-10-27 09:41:08,731 INFO [Reconnect to Cluster] o.apache.nifi.controller.FlowController Will no longer send heartbeats
2023-10-27 09:41:08,731 INFO [Reconnect to Cluster] o.apache.nifi.controller.FlowController FlowController will stop sending heartbeats to Cluster Coordinator
2023-10-27 09:41:08,731 INFO [Reconnect to Cluster] o.apache.nifi.controller.FlowController Cluster State changed from Clustered to Not Clustered
2023-10-27 09:41:08,731 INFO [Reconnect to Cluster] o.a.n.c.l.e.CuratorLeaderElectionManager Cannot unregister Leader Election Role 'Primary Node' because that role is not registered
<REMOVED FOR READABILITY>
2023-10-27 09:41:08,731 ERROR [Reconnect to Cluster] o.a.nifi.controller.StandardFlowService Handling reconnection request failed due to: org.apache.nifi.controller.serialization.FlowSynchronizationException: Failed to connect node to cluster because local flow controller partially updated. Administrator should disconnect node and review flow for corruption.
org.apache.nifi.controller.serialization.FlowSynchronizationException: Failed to connect node to cluster because local flow controller partially updated. Administrator should disconnect node and review flow for corruption.
at org.apache.nifi.controller.StandardFlowService.loadFromConnectionResponse(StandardFlowService.java:1059)
<REMOVED FOR READABILITY>
at java.base/java.lang.Thread.run(Thread.java:829)
Caused by: org.apache.nifi.controller.serialization.FlowSynchronizationException: java.lang.IllegalStateException: Cannot change destination of Connection because the current destination is running
at org.apache.nifi.controller.serialization.VersionedFlowSynchronizer.synchronizeFlow(VersionedFlowSynchronizer.java:448)
<REMOVED FOR READABILITY>
... 4 common frames omitted
Caused by: java.lang.IllegalStateException: Cannot change destination of Connection because the current destination is running
at org.apache.nifi.connectable.StandardConnection.setDestination(StandardConnection.java:310)
at org.apache.nifi.flow.synchronization.StandardVersionedComponentSynchronizer.updateConnectionDestinations(StandardVersionedComponentSynchronizer.java:700)
at org.apache.nifi.flow.synchronization.StandardVersionedComponentSynchronizer.synchronize(StandardVersionedComponentSynchronizer.java:405)
<REMOVED FOR READABILITY>
... 10 common frames omitted
2023-10-27 09:41:08,732 INFO [Reconnect to Cluster] o.a.n.c.c.node.NodeClusterCoordinator node1.nifi:9441 requested disconnection from cluster due to org.apache.nifi.controller.serialization.FlowSynchronizationException: Failed to connect node to cluster because local flow controller partially updated. Administrator should disconnect node and review flow for corruption.
2023-10-27 09:41:08,732 INFO [Reconnect to Cluster] o.a.n.c.c.node.NodeClusterCoordinator Status of node1.nifi:9441 changed from NodeConnectionStatus[nodeId=node1.nifi:9441, state=CONNECTING, updateId=84] to NodeConnectionStatus[nodeId=node1.nifi:9441, state=DISCONNECTED, Disconnect Code=Node's Flow did not Match Cluster Flow, Disconnect Reason=org.apache.nifi.controller.serialization.FlowSynchronizationException: Failed to connect node to cluster because local flow controller partially updated. Administrator should disconnect node and review flow for corruption., updateId=86]{code}
In your cluster, do you see anything similar to the logs starting at 2023-10-27 09:41:08,722? Specifically, I see:
# Confirmation that there was no conflicts between current and proposed flows
# A funnel added into a *processor group*
# NiFi attempts to start processors but none listed
# Failure message due to "partially updated" local flow
# Stack trace on this error has "Cannot change destination of Connection because the current destination is running" - This is in your logs as well
# Any subsequent reconnect attempts fail for the same reason until restarting node
When I view the disconnected node in a web browser, I can steal see that funnel in the processor group - removing it doesn't result in a successful reconnect attempt, albeit with limited testing.
h3. Steps to Recreate:
# Follow all steps of [https://nifi.apache.org/docs/nifi-docs/html/walkthroughs.html#creating-and-securing-a-nifi-cluster-with-the-tls-toolkit]
# Set nifi.cluster.protocol.heartbeat.interval=5 sec => nifi.cluster.protocol.heartbeat.interval=3 sec (see Note 1)
# Set nifi.cluster.protocol.heartbeat.missable.max=8 =>
nifi.cluster.protocol.heartbeat.missable.max=1 (see Note 1)
# On the main canvas, make a simple flow. For me, I had a getFile to a test folder with some large zip files => UpdateAttribute ${filename}1 => putFile in test folder. I don't think this workflow is directly related but this was created with large files to load the system/use memory. Turn on the processors.
# Create a template out of this flow
# Add a processor group to the canvas and enter group
# Place created template on canvas and turn on processors
# At this point, the nodes start dropping from cluster locally within about 1 minute and all have disconnected (with their own temp-funnel in the processor group) from the cluster.
Note 1: These are set to intentionally induce a disconnect due to lack of heartbeats. The actual cluster uses these default values but the system will occasionally hang for extended periods, causing a disconnect for the same reason as these steps.
I did notice that after restarting the cluster, to reproduce the error an additional time I had to start at step 6 in the added template from the first time. It seems like adding a new processor group is required to reproduce. I cannot confirm that this has always happened in the production clusters, but it is fairly common for new processor groups to be added while running. From the screenshot included on the original post, we both seem to have processor groups present.
Again, if you don't think we are experiencing the same bug in reconnection logic, please let me know and I'll open a ticket to track this all separately.
Thanks!
was (Author: JIRAUSER302821):
Hello,
I am also having a number of the "Failed to connect node to cluster..." errors in my system leaving nodes disconnected from the cluster until stopping NiFi and allowing the node to recreate its canvas from the cluster. I am trying to determine if we are experiencing same issues or if this should be its own ticket.
My logs immediately before the "Failed to connect ..." errors look like:
{code:java}
2023-10-27 09:41:08,373 INFO [Heartbeat Monitor Thread-1] o.a.n.c.c.node.NodeClusterCoordinator Status of node1.nifi:9441 changed from NodeConnectionStatus[nodeId=node1.nifi:9441, state=DISCONNECTED, Disconnect Code=Lack of Heartbeat, Disconnect Reason=Have not received a heartbeat from node in 3 seconds, updateId=83] to NodeConnectionStatus[nodeId=node1.nifi:9441, state=CONNECTING, updateId=84]
<REMOVED FOR READABILITY>
2023-10-27 09:41:08,452 INFO [Reconnect to Cluster] o.a.nifi.controller.StandardFlowService Processing reconnection request from cluster coordinator.
<REMOVED FOR READABILITY>
2023-10-27 09:41:08,720 INFO [Reconnect to Cluster] o.a.nifi.groups.StandardProcessGroup Template[id=9cd572fa-2d18-3228-9a10-8f2438ae9459] removed from flow
2023-10-27 09:41:08,722 INFO [Reconnect to Cluster] o.a.n.f.s.StandardVersionedComponentSynchronizer No differences between current flow and proposed flow for StandardProcessGroup[identifier=4e8898ea-018b-1000-14a4-b336fae6590e,name=NiFi Flow]
2023-10-27 09:41:08,724 INFO [Reconnect to Cluster] o.a.nifi.groups.StandardProcessGroup StandardFunnel[id=71590595-018b-1000-ffff-ffff94fe7f50-temp-funnel] added to StandardProcessGroup[identifier=71590595-018b-1000-ffff-ffff94fe7f50,name=testetst]
2023-10-27 09:41:08,731 INFO [Reconnect to Cluster] o.a.n.c.s.AffectedComponentSet Starting the following components: AffectedComponentSet[inputPorts=[], outputPorts=[], remoteInputPorts=[], remoteOutputPorts=[], processors=[], parameterProviders=[], flowRegistryCliens=[], controllerServices=[], reportingTasks=[]]
2023-10-27 09:41:08,731 INFO [Reconnect to Cluster] o.a.nifi.controller.StandardFlowService Disconnecting node due to Failed to properly handle Reconnection request due to org.apache.nifi.controller.serialization.FlowSynchronizationException: Failed to connect node to cluster because local flow controller partially updated. Administrator should disconnect node and review flow for corruption.
2023-10-27 09:41:08,731 INFO [Reconnect to Cluster] o.apache.nifi.controller.FlowController Will no longer send heartbeats
2023-10-27 09:41:08,731 INFO [Reconnect to Cluster] o.apache.nifi.controller.FlowController FlowController will stop sending heartbeats to Cluster Coordinator
2023-10-27 09:41:08,731 INFO [Reconnect to Cluster] o.apache.nifi.controller.FlowController Cluster State changed from Clustered to Not Clustered
2023-10-27 09:41:08,731 INFO [Reconnect to Cluster] o.a.n.c.l.e.CuratorLeaderElectionManager Cannot unregister Leader Election Role 'Primary Node' because that role is not registered
<REMOVED FOR READABILITY>
2023-10-27 09:41:08,731 ERROR [Reconnect to Cluster] o.a.nifi.controller.StandardFlowService Handling reconnection request failed due to: org.apache.nifi.controller.serialization.FlowSynchronizationException: Failed to connect node to cluster because local flow controller partially updated. Administrator should disconnect node and review flow for corruption.
org.apache.nifi.controller.serialization.FlowSynchronizationException: Failed to connect node to cluster because local flow controller partially updated. Administrator should disconnect node and review flow for corruption.
at org.apache.nifi.controller.StandardFlowService.loadFromConnectionResponse(StandardFlowService.java:1059)
<REMOVED FOR READABILITY>
at java.base/java.lang.Thread.run(Thread.java:829)
Caused by: org.apache.nifi.controller.serialization.FlowSynchronizationException: java.lang.IllegalStateException: Cannot change destination of Connection because the current destination is running
at org.apache.nifi.controller.serialization.VersionedFlowSynchronizer.synchronizeFlow(VersionedFlowSynchronizer.java:448)
<REMOVED FOR READABILITY>
... 4 common frames omitted
Caused by: java.lang.IllegalStateException: Cannot change destination of Connection because the current destination is running
at org.apache.nifi.connectable.StandardConnection.setDestination(StandardConnection.java:310)
at org.apache.nifi.flow.synchronization.StandardVersionedComponentSynchronizer.updateConnectionDestinations(StandardVersionedComponentSynchronizer.java:700)
at org.apache.nifi.flow.synchronization.StandardVersionedComponentSynchronizer.synchronize(StandardVersionedComponentSynchronizer.java:405)
<REMOVED FOR READABILITY>
... 10 common frames omitted
2023-10-27 09:41:08,732 INFO [Reconnect to Cluster] o.a.n.c.c.node.NodeClusterCoordinator node1.nifi:9441 requested disconnection from cluster due to org.apache.nifi.controller.serialization.FlowSynchronizationException: Failed to connect node to cluster because local flow controller partially updated. Administrator should disconnect node and review flow for corruption.
2023-10-27 09:41:08,732 INFO [Reconnect to Cluster] o.a.n.c.c.node.NodeClusterCoordinator Status of node1.nifi:9441 changed from NodeConnectionStatus[nodeId=node1.nifi:9441, state=CONNECTING, updateId=84] to NodeConnectionStatus[nodeId=node1.nifi:9441, state=DISCONNECTED, Disconnect Code=Node's Flow did not Match Cluster Flow, Disconnect Reason=org.apache.nifi.controller.serialization.FlowSynchronizationException: Failed to connect node to cluster because local flow controller partially updated. Administrator should disconnect node and review flow for corruption., updateId=86]{code}
In your cluster, do you see anything similar to the logs starting at 2023-10-27 09:41:08,722? Specifically, I see:
# Confirmation that there was no conflicts between current and proposed flows
# A funnel added into a *processor group*
# NiFi attempts to start processors but none listed
# Failure message due to "partially updated" local flow
# Stack trace on this error has "Cannot change destination of Connection because the current destination is running"
# Any subsequent reconnect attempts fail for the same reason until restarting node
When I view the disconnected node in a web browser, I can steal see that funnel in the processor group - removing it doesn't result in a successful reconnect attempt, albeit with limited testing.
h3. Steps to Recreate:
# Follow all steps of [https://nifi.apache.org/docs/nifi-docs/html/walkthroughs.html#creating-and-securing-a-nifi-cluster-with-the-tls-toolkit]
# Set nifi.cluster.protocol.heartbeat.interval=5 sec => nifi.cluster.protocol.heartbeat.interval=3 sec (see Note 1)
# Set nifi.cluster.protocol.heartbeat.missable.max=8 =>
nifi.cluster.protocol.heartbeat.missable.max=1 (see Note 1)
# On the main canvas, make a simple flow. For me, I had a getFile to a test folder with some large zip files => UpdateAttribute ${filename}1 => putFile in test folder. I don't think this workflow is directly related but this was created with large files to load the system/use memory. Turn on the processors.
# Create a template out of this flow
# Add a processor group to the canvas and enter group
# Place created template on canvas and turn on processors
# At this point, the nodes start dropping from cluster locally within about 1 minute and all have disconnected (with their own temp-funnel in the processor group) from the cluster.
Note 1: These are set to intentionally induce a disconnect due to lack of heartbeats. The actual cluster uses these default values but the system will occasionally hang for extended periods, causing a disconnect for the same reason as these steps.
I did notice that after restarting the cluster, to reproduce the error an additional time I had to start at step 6 in the added template from the first time. It seems like adding a new processor group is required to reproduce. I cannot confirm that this has always happened in the production clusters, but it is fairly common for new processor groups to be added while running. From the screenshot included on the original post, we both seem to have processor groups present.
Again, if you don't think we are experiencing the same bug in reconnection logic, please let me know and I'll open a ticket to track this all separately.
Thanks!
> Frequent "failed to connect node to cluster because local flow controller partially updated. Administrator should disconnect node and review flow for corruption"
> -----------------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: NIFI-12232
> URL: https://issues.apache.org/jira/browse/NIFI-12232
> Project: Apache NiFi
> Issue Type: Bug
> Components: Configuration Management
> Affects Versions: 1.23.2
> Reporter: John Joseph
> Priority: Major
> Attachments: image-2023-10-16-16-12-31-027.png
>
>
> This is an issue that we have been observing in the 1.23.2 version of NiFi when we try upgrade,
> Since Rolling upgrade is not supported in NiFi, we scale out the revision that is running and {_}run a helm upgrade{_}.
> We have NIFI running in k8s cluster mode, there is a post job that call the Tenants and policies API. On a successful run it would run like this
> {code:java}
> set_policies() Action: 'read' Resource: '/flow' entity_id: 'ad2d3ad6-5d69-3e0f-95e9-c7feb36e2de5' entity_name: 'CN=nifi-api-admin' entity_type: 'USER'
> set_policies() status: '200'
> 'read' '/flow' policy already exists. It will be updated...
> set_policies() fetching policy inside -eq 200 status: '200'
> set_policies() after update PUT: '200'
> set_policies() Action: 'read' Resource: '/tenants' entity_id: 'ad2d3ad6-5d69-3e0f-95e9-c7feb36e2de5' entity_name: 'CN=nifi-api-admin' entity_type: 'USER'
> set_policies() status: '200'{code}
> *_This job was running fine in 1.23.0, 1.22 and other previous versions._* In {*}{{1.23.2}}{*}, we are noticing that the job is failing very frequently with the error logs;
> {code:java}
> set_policies() Action: 'read' Resource: '/flow' entity_id: 'ad2d3ad6-5d69-3e0f-95e9-c7feb36e2de5' entity_name: 'CN=nifi-api-admin' entity_type: 'USER'
> set_policies() status: '200'
> 'read' '/flow' policy already exists. It will be updated...
> set_policies() fetching policy inside -eq 200 status: '200'
> set_policies() after update PUT: '400'
> An error occurred getting 'read' '/flow' policy: 'This node is disconnected from its configured cluster. The requested change will only be allowed if the flag to acknowledge the disconnected node is set.'{code}
> {{_*'This node is disconnected from its configured cluster. The requested change will only be allowed if the flag to acknowledge the disconnected node is set.'*_}}
> The job is configured to run only after all the pods are up and running. Though the pods are up we see exception is the inside pods
> {code:java}
> org.apache.nifi.controller.serialization.FlowSynchronizationException: Failed to connect node to cluster because local flow controller partially updated. Administrator should disconnect node and review flow for corruption.
> at org.apache.nifi.controller.StandardFlowService.loadFromConnectionResponse(StandardFlowService.java:1059)
> at org.apache.nifi.controller.StandardFlowService.handleReconnectionRequest(StandardFlowService.java:667)
> at org.apache.nifi.controller.StandardFlowService.access$200(StandardFlowService.java:107)
> at org.apache.nifi.controller.StandardFlowService$1.run(StandardFlowService.java:396)
> at java.base/java.lang.Thread.run(Thread.java:833)
> Caused by: org.apache.nifi.controller.serialization.FlowSynchronizationException: java.lang.IllegalStateException: Cannot change destination of Connection because the current destination is running
> at org.apache.nifi.controller.serialization.VersionedFlowSynchronizer.synchronizeFlow(VersionedFlowSynchronizer.java:448)
> at org.apache.nifi.controller.serialization.VersionedFlowSynchronizer.sync(VersionedFlowSynchronizer.java:206)
> at org.apache.nifi.controller.serialization.StandardFlowSynchronizer.sync(StandardFlowSynchronizer.java:42)
> at org.apache.nifi.controller.FlowController.synchronize(FlowController.java:1530)
> at org.apache.nifi.persistence.StandardFlowConfigurationDAO.load(StandardFlowConfigurationDAO.java:104)
> at org.apache.nifi.controller.StandardFlowService.loadFromBytes(StandardFlowService.java:817)
> at org.apache.nifi.controller.StandardFlowService.loadFromConnectionResponse(StandardFlowService.java:1028)
> ... 4 common frames omitted
> Caused by: java.lang.IllegalStateException: Cannot change destination of Connection because the current destination is running
> at org.apache.nifi.connectable.StandardConnection.setDestination(StandardConnection.java:310)
> at org.apache.nifi.flow.synchronization.StandardVersionedComponentSynchronizer.updateConnectionDestinations(StandardVersionedComponentSynchronizer.java:700)
> at org.apache.nifi.flow.synchronization.StandardVersionedComponentSynchronizer.synchronize(StandardVersionedComponentSynchronizer.java:405)
> at org.apache.nifi.flow.synchronization.StandardVersionedComponentSynchronizer.synchronizeChildGroups(StandardVersionedComponentSynchronizer.java:543)
> at org.apache.nifi.flow.synchronization.StandardVersionedComponentSynchronizer.synchronize(StandardVersionedComponentSynchronizer.java:427)
> at org.apache.nifi.flow.synchronization.StandardVersionedComponentSynchronizer.lambda$synchronize$0(StandardVersionedComponentSynchronizer.java:266)
> at org.apache.nifi.controller.flow.AbstractFlowManager.withParameterContextResolution(AbstractFlowManager.java:550)
> at org.apache.nifi.flow.synchronization.StandardVersionedComponentSynchronizer.synchronize(StandardVersionedComponentSynchronizer.java:261)
> at org.apache.nifi.groups.StandardProcessGroup.synchronizeFlow(StandardProcessGroup.java:3977)
> at org.apache.nifi.controller.serialization.VersionedFlowSynchronizer.synchronizeFlow(VersionedFlowSynchronizer.java:439)
> ... 10 common frames omitted{code}
> Attaching screenshots of the UI as well. this issue is observed a lot checking with CLI command.
> {code:java}
> ./cli.sh nifi cluster-summary -u https://nifi-headless.doc-norc.svc.cluster.local:9443 -ts /opt/nifi/cert_mgr/truststore.jks -tst jks -tsp changeit -ks /opt/nifi/cert_mgr/keystore.j
> ks -kst jks -ksp changeit
> Total node count: 0
> Connected node count: 0
> Clustered: true
> Connected to cluster: false{code}
>
> We tried Workaround
> {code:java}
> 1.Exec to the pod that has the flow file issue, delete the flow file so that it deletes from the PVC
> 2. Exit from pod
> 3. Delete the pod that had the problem{code}
> Pod will respwan, cluster coordinator will recreate the flowfile from the connected nodes
> This connected all the nodes. But this does not feel like an ideal solution as we're seeing this issue quite often and cannot run this WA every time
> !image-2023-10-16-16-12-31-027.png!
>
> we also see this Exception sometimes
> {code:java}
> org.apache.zookeeper.KeeperException$ConnectionLossException: KeeperErrorCode = ConnectionLoss for /nifi/leaders/Cluster Coordinator
> at org.apache.zookeeper.KeeperException.create(KeeperException.java:102)
> at org.apache.zookeeper.KeeperException.create(KeeperException.java:54)
> at org.apache.zookeeper.ZooKeeper.getChildren(ZooKeeper.java:2480)
> at org.apache.curator.framework.imps.GetChildrenBuilderImpl$3.call(GetChildrenBuilderImpl.java:243)
> at org.apache.curator.framework.imps.GetChildrenBuilderImpl$3.call(GetChildrenBuilderImpl.java:232)
> at org.apache.curator.RetryLoop.callWithRetry(RetryLoop.java:94)
> at org.apache.curator.framework.imps.GetChildrenBuilderImpl.pathInForeground(GetChildrenBuilderImpl.java:229)
> at org.apache.curator.framework.imps.GetChildrenBuilderImpl.forPath(GetChildrenBuilderImpl.java:220)
> at org.apache.curator.framework.imps.GetChildrenBuilderImpl.forPath(GetChildrenBuilderImpl.java:42)
> at org.apache.curator.framework.recipes.locks.LockInternals.getSortedChildren(LockInternals.java:155)
> at org.apache.curator.framework.recipes.locks.LockInternals.getParticipantNodes(LockInternals.java:135)
> at org.apache.curator.framework.recipes.locks.InterProcessMutex.getParticipantNodes(InterProcessMutex.java:170)
> at org.apache.curator.framework.recipes.leader.LeaderSelector.getLeader(LeaderSelector.java:336)
> at org.apache.nifi.controller.leader.election.CuratorLeaderElectionManager.getLeader(CuratorLeaderElectionManager.java:281)
> at org.apache.nifi.controller.leader.election.CuratorLeaderElectionManager$ElectionListener.verifyLeader(CuratorLeaderElectionManager.java:572)
> at org.apache.nifi.controller.leader.election.CuratorLeaderElectionManager$ElectionListener.isLeader(CuratorLeaderElectionManager.java:526)
> at org.apache.nifi.controller.leader.election.CuratorLeaderElectionManager$LeaderRole.isLeader(CuratorLeaderElectionManager.java:467)
> at org.apache.nifi.controller.leader.election.CuratorLeaderElectionManager.isLeader(CuratorLeaderElectionManager.java:262)
> at org.apache.nifi.cluster.coordination.node.NodeClusterCoordinator.isActiveClusterCoordinator(NodeClusterCoordinator.java:824)
> at org.apache.nifi.cluster.coordination.heartbeat.AbstractHeartbeatMonitor.monitorHeartbeats(AbstractHeartbeatMonitor.java:132)
> at org.apache.nifi.cluster.coordination.heartbeat.AbstractHeartbeatMonitor$1.run(AbstractHeartbeatMonitor.java:84)
> at org.apache.nifi.engine.FlowEngine$2.run(FlowEngine.java:110){code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)