<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>question Re: Nifi : Unable to elect cluster coordinator in Support Questions</title>
    <link>https://community.cloudera.com/t5/Support-Questions/Nifi-Unable-to-elect-cluster-coordinator/m-p/395819#M249033</link>
    <description>&lt;P&gt;&lt;a href="https://community.cloudera.com/t5/user/viewprofilepage/user-id/118267"&gt;@vg27&lt;/a&gt;&amp;nbsp;&lt;BR /&gt;&lt;BR /&gt;If you have a support contract with Cloudera, you could open a support case where someone could connect directly with you and assist you through your many issues.&lt;BR /&gt;&lt;BR /&gt;------&lt;BR /&gt;1. As i have shared before, the Single-User providers are not designed with the intent of use in a NiFi clustered environment.&amp;nbsp; They should only be used for standalone NiFi evaluation purposes.&amp;nbsp; Once you start to get in to the more involved cluster based deployments, you need to use different providers for authentication and authorization.&amp;nbsp; When using the single-user-provider for authentication, each node can create different credentials which will not work in a cluster environment.&amp;nbsp; &amp;nbsp;&lt;BR /&gt;&lt;BR /&gt;For login based authentication, you should be using LDAP/AD (ldap-provider) or Kerberos (Kerberos-provider).&amp;nbsp;&lt;BR /&gt;&lt;BR /&gt;For authorization, you should be using the managed authorizer.&amp;nbsp;&lt;BR /&gt;&lt;BR /&gt;------&lt;/P&gt;&lt;P&gt;2. Are you still using your own generated keystore and truststore with your own created private and public certificates?&amp;nbsp; Using the NiFi auto-generated keystore and truststore will also not support clustering well as each node will not have a common certificate authority.&amp;nbsp;&lt;BR /&gt;&lt;BR /&gt;-----&lt;BR /&gt;3. The "&lt;SPAN&gt;org.apache.zookeeper.KeeperException$ConnectionLossException: KeeperErrorCode = ConnectionLoss" exception is an issue with with Zookeeper (ZK) Quorum.&amp;nbsp; This error can happen if both you nodes are not fully up at time of exception and may also happen because you do not have proper quorum with your ZK.&amp;nbsp; Quorum consists of and odd number of ZK hosts with min 3.&amp;nbsp; Strongly encourage the use of an external ZK since anytime one of your nodes goes down, you'll lose access to both nodes.&lt;BR /&gt;&lt;BR /&gt;-----&lt;BR /&gt;4. You are using an external https Load Balancer (LB) which means that sticky sessions (session affinity) must be setup since the user token issues when you login is only valid for use with the node that issued it.&amp;nbsp; So if your LB directs you to node 1 that presents you with login UI, you enter credentials obtaining a user token from node 1, and your LB then redirects to node 2 to load UI, it will fail authentication on node 2 because the request includes the token only good for node 1.&amp;nbsp;&lt;BR /&gt;&lt;BR /&gt;-----&lt;BR /&gt;5. I see you are using a mix of hostnames and IP addresses in your NiFi configurations, so make sure that the node certificates include both as SAN entries to avoid issues.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;-----&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Please help our community thrive. If you found&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;STRONG&gt;any&lt;/STRONG&gt;&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;of the suggestions/solutions provided helped you with solving your issue or answering your question, please take a moment to login and click "&lt;SPAN&gt;&lt;EM&gt;&lt;STRONG&gt;&lt;FONT color="#FF0000"&gt;Accept as Solution&lt;/FONT&gt;&lt;/STRONG&gt;&lt;/EM&gt;" on&amp;nbsp;&lt;STRONG&gt;one or more&lt;/STRONG&gt;&amp;nbsp;of them that helped.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;Thank you,&lt;BR /&gt;Matt&lt;/SPAN&gt;&lt;/P&gt;</description>
    <pubDate>Wed, 23 Oct 2024 13:02:18 GMT</pubDate>
    <dc:creator>MattWho</dc:creator>
    <dc:date>2024-10-23T13:02:18Z</dc:date>
    <item>
      <title>Nifi : Unable to elect cluster coordinator</title>
      <link>https://community.cloudera.com/t5/Support-Questions/Nifi-Unable-to-elect-cluster-coordinator/m-p/395748#M249013</link>
      <description>&lt;P&gt;HI&amp;nbsp;&lt;a href="https://community.cloudera.com/t5/user/viewprofilepage/user-id/35454"&gt;@MattWho&lt;/a&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;client asked us to use the common username and password kind of authority, instead of certificate based, so i re-created the&amp;nbsp; NIFI components&amp;nbsp; &amp;nbsp;to private VM's NIFI nodes, using the https load balancer,&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;Burt now getting the different error:&amp;nbsp;&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;2024-10-22 15:46:17,574 INFO [main] o.a.nifi.controller.StandardFlowService Connecting Node: 53.13.138.70:8443&lt;BR /&gt;2024-10-22 15:46:20,785 WARN [Heartbeat Monitor Thread-1] o.a.n.c.l.e.CuratorLeaderElectionManager Unable to determine leader for role 'Cluster Coordinator'; returning null&lt;BR /&gt;org.apache.zookeeper.KeeperException$ConnectionLossException: KeeperErrorCode = ConnectionLoss for /nifi/leaders/Cluster Coordinator&lt;BR /&gt;at org.apache.zookeeper.KeeperException.create(KeeperException.java:101)&lt;BR /&gt;at org.apache.zookeeper.KeeperException.create(KeeperException.java:53)&lt;BR /&gt;at org.apache.zookeeper.ZooKeeper.getChildren(ZooKeeper.java:2480)&lt;BR /&gt;at org.apache.curator.framework.imps.GetChildrenBuilderImpl$3.call(GetChildrenBuilderImpl.java:235)&lt;BR /&gt;at org.apache.curator.framework.imps.GetChildrenBuilderImpl$3.call(GetChildrenBuilderImpl.java:228)&lt;BR /&gt;at org.apache.curator.RetryLoop.callWithRetry(RetryLoop.java:88)&lt;BR /&gt;at org.apache.curator.framework.imps.GetChildrenBuilderImpl.pathInForeground(GetChildrenBuilderImpl.java:228)&lt;BR /&gt;at org.apache.curator.framework.imps.GetChildrenBuilderImpl.forPath(GetChildrenBuilderImpl.java:221)&lt;BR /&gt;at org.apache.curator.framework.imps.GetChildrenBuilderImpl.forPath(GetChildrenBuilderImpl.java:42)&lt;BR /&gt;at org.apache.curator.framework.recipes.locks.LockInternals.getSortedChildren(LockInternals.java:133)&lt;BR /&gt;at org.apache.curator.framework.recipes.locks.LockInternals.getParticipantNodes(LockInternals.java:119)&lt;BR /&gt;at org.apache.curator.framework.recipes.locks.InterProcessMutex.getParticipantNodes(InterProcessMutex.java:153)&lt;BR /&gt;at org.apache.curator.framework.recipes.leader.LeaderSelector.getLeader(LeaderSelector.java:321)&lt;BR /&gt;at org.apache.nifi.controller.leader.election.CuratorLeaderElectionManager.getLeader(CuratorLeaderElectionManager.java:288)&lt;BR /&gt;at org.apache.nifi.controller.leader.election.CuratorLeaderElectionManager$ElectionListener.verifyLeader(CuratorLeaderElectionManager.java:579)&lt;BR /&gt;at org.apache.nifi.controller.leader.election.CuratorLeaderElectionManager$ElectionListener.isLeader(CuratorLeaderElectionManager.java:533)&lt;BR /&gt;at org.apache.nifi.controller.leader.election.CuratorLeaderElectionManager$LeaderRole.isLeader(CuratorLeaderElectionManager.java:474)&lt;BR /&gt;at org.apache.nifi.controller.leader.election.CuratorLeaderElectionManager.isLeader(CuratorLeaderElectionManager.java:269)&lt;BR /&gt;at org.apache.nifi.cluster.coordination.node.NodeClusterCoordinator.isActiveClusterCoordinator(NodeClusterCoordinator.java:824)&lt;BR /&gt;at org.apache.nifi.cluster.coordination.heartbeat.AbstractHeartbeatMonitor.monitorHeartbeats(AbstractHeartbeatMonitor.java:132)&lt;BR /&gt;at org.apache.nifi.cluster.coordination.heartbeat.AbstractHeartbeatMonitor$1.run(AbstractHeartbeatMonitor.java:84)&lt;BR /&gt;at org.apache.nifi.engine.FlowEngine$2.run(FlowEngine.java:110)&lt;BR /&gt;at java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:515)&lt;BR /&gt;at java.base/java.util.concurrent.FutureTask.runAndReset(FutureTask.java:305)&lt;BR /&gt;at java.base/java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:305)&lt;BR /&gt;at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)&lt;BR /&gt;at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)&lt;BR /&gt;at java.base/java.lang.Thread.run(Thread.java:829)&lt;BR /&gt;2024-10-22 15:46:20,788 INFO [Curator-ConnectionStateManager-0] o.a.n.c.l.e.CuratorLeaderElectionManager org.apache.nifi.controller.leader.election.CuratorLeaderElectionManager$ElectionListe&lt;BR /&gt;ner@58c1da45 Connection State changed to SUSPENDED&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Based on the last recommendations from the below link i identified the state file directory instead of removing it, i rename that state file directory.&lt;/P&gt;&lt;P&gt;&lt;A href="https://community.cloudera.com/t5/Support-Questions/Nifi-Unable-to-elect-cluster-coordinator/m-p/333527" target="_blank" rel="noopener"&gt;https://community.cloudera.com/t5/Support-Questions/Nifi-Unable-to-elect-cluster-coordinator/m-p/333527&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;Attaching the screenshot for your reference&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="vg27_0-1729612438804.png" style="width: 400px;"&gt;&lt;img src="https://community.cloudera.com/t5/image/serverpage/image-id/42307iC2985CF7CE31727D/image-size/medium?v=v2&amp;amp;px=400" role="button" title="vg27_0-1729612438804.png" alt="vg27_0-1729612438804.png" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;P&gt;********************************************************************************************************&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;providing the nifi properties file&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;# Licensed to the Apache Software Foundation (ASF) under one or more&lt;BR /&gt;# contributor license agreements. See the NOTICE file distributed with&lt;BR /&gt;# this work for additional information regarding copyright ownership.&lt;BR /&gt;# The ASF licenses this file to You under the Apache License, Version 2.0&lt;BR /&gt;# (the "License"); you may not use this file except in compliance with&lt;BR /&gt;# the License. You may obtain a copy of the License at&lt;BR /&gt;#&lt;BR /&gt;# &lt;A href="http://www.apache.org/licenses/LICENSE-2.0" target="_blank" rel="noopener"&gt;http://www.apache.org/licenses/LICENSE-2.0&lt;/A&gt;&lt;BR /&gt;#&lt;BR /&gt;# Unless required by applicable law or agreed to in writing, software&lt;BR /&gt;# distributed under the License is distributed on an "AS IS" BASIS,&lt;BR /&gt;# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.&lt;BR /&gt;# See the License for the specific language governing permissions and&lt;BR /&gt;# limitations under the License.&lt;/P&gt;&lt;P&gt;# Core Properties #&lt;BR /&gt;nifi.flow.configuration.file=./conf/flow.xml.gz&lt;BR /&gt;nifi.flow.configuration.json.file=./conf/flow.json.gz&lt;BR /&gt;nifi.flow.configuration.archive.enabled=true&lt;BR /&gt;nifi.flow.configuration.archive.dir=./conf/archive/&lt;BR /&gt;nifi.flow.configuration.archive.max.time=30 days&lt;BR /&gt;nifi.flow.configuration.archive.max.storage=500 MB&lt;BR /&gt;nifi.flow.configuration.archive.max.count=&lt;BR /&gt;nifi.flowcontroller.autoResumeState=true&lt;BR /&gt;nifi.flowcontroller.graceful.shutdown.period=10 sec&lt;BR /&gt;nifi.flowservice.writedelay.interval=500 ms&lt;BR /&gt;nifi.administrative.yield.duration=30 sec&lt;BR /&gt;# If a component has no work to do (is "bored"), how long should we wait before checking again for work?&lt;BR /&gt;nifi.bored.yield.duration=10 millis&lt;BR /&gt;nifi.queue.backpressure.count=10000&lt;BR /&gt;nifi.queue.backpressure.size=1 GB&lt;/P&gt;&lt;P&gt;nifi.authorizer.configuration.file=./conf/authorizers.xml&lt;BR /&gt;nifi.login.identity.provider.configuration.file=./conf/login-identity-providers.xml&lt;BR /&gt;nifi.templates.directory=./conf/templates&lt;BR /&gt;nifi.ui.banner.text=&lt;BR /&gt;nifi.ui.autorefresh.interval=30 sec&lt;BR /&gt;nifi.nar.library.directory=./lib&lt;BR /&gt;nifi.nar.library.autoload.directory=./extensions&lt;BR /&gt;nifi.nar.working.directory=./work/nar/&lt;BR /&gt;nifi.documentation.working.directory=./work/docs/components&lt;BR /&gt;nifi.nar.unpack.uber.jar=false&lt;/P&gt;&lt;P&gt;####################&lt;BR /&gt;# State Management #&lt;BR /&gt;####################&lt;/P&gt;&lt;P&gt;####################&lt;BR /&gt;nifi.state.management.configuration.file=./conf/state-management.xml&lt;BR /&gt;# The ID of the local state provider&lt;BR /&gt;nifi.state.management.provider.local=local-provider&lt;BR /&gt;# The ID of the cluster-wide state provider. This will be ignored if NiFi is not clustered but must be populated if running in a cluster.&lt;BR /&gt;nifi.state.management.provider.cluster=zk-provider&lt;BR /&gt;# Specifies whether or not this instance of NiFi should run an embedded ZooKeeper server&lt;BR /&gt;nifi.state.management.embedded.zookeeper.start=false&lt;BR /&gt;# Properties file that provides the ZooKeeper properties to use if &amp;lt;nifi.state.management.embedded.zookeeper.start&amp;gt; is set to true&lt;BR /&gt;nifi.state.management.embedded.zookeeper.properties=./conf/zookeeper.properties&lt;/P&gt;&lt;P&gt;# Database Settings&lt;BR /&gt;nifi.database.directory=./database_repository&lt;/P&gt;&lt;P&gt;# Repository Encryption properties override individual repository implementation properties&lt;BR /&gt;nifi.repository.encryption.protocol.version=&lt;BR /&gt;nifi.repository.encryption.key.id=&lt;BR /&gt;nifi.repository.encryption.key.provider=&lt;BR /&gt;nifi.repository.encryption.key.provider.keystore.location=&lt;BR /&gt;nifi.repository.encryption.key.provider.keystore.password=&lt;/P&gt;&lt;P&gt;# FlowFile Repository&lt;BR /&gt;nifi.flowfile.repository.implementation=org.apache.nifi.controller.repository.WriteAheadFlowFileRepository&lt;BR /&gt;nifi.flowfile.repository.wal.implementation=org.apache.nifi.wali.SequentialAccessWriteAheadLog&lt;BR /&gt;nifi.flowfile.repository.directory=./flowfile_repository&lt;BR /&gt;nifi.flowfile.repository.checkpoint.interval=20 secs&lt;BR /&gt;nifi.flowfile.repository.always.sync=false&lt;BR /&gt;nifi.flowfile.repository.retain.orphaned.flowfiles=true&lt;/P&gt;&lt;P&gt;nifi.swap.manager.implementation=org.apache.nifi.controller.FileSystemSwapManager&lt;BR /&gt;nifi.queue.swap.threshold=20000&lt;/P&gt;&lt;P&gt;# Content Repository&lt;BR /&gt;nifi.content.repository.implementation=org.apache.nifi.controller.repository.FileSystemRepository&lt;BR /&gt;nifi.content.claim.max.appendable.size=50 KB&lt;BR /&gt;nifi.content.repository.directory.default=./content_repository&lt;BR /&gt;nifi.content.repository.archive.max.retention.period=7 days&lt;BR /&gt;nifi.content.repository.archive.max.usage.percentage=50%&lt;BR /&gt;nifi.content.repository.archive.enabled=true&lt;BR /&gt;nifi.content.repository.always.sync=false&lt;BR /&gt;nifi.content.viewer.url=../nifi-content-viewer/&lt;/P&gt;&lt;P&gt;# Provenance Repository Properties&lt;BR /&gt;nifi.provenance.repository.implementation=org.apache.nifi.provenance.WriteAheadProvenanceRepository&lt;/P&gt;&lt;P&gt;nifi.provenance.repository.implementation=org.apache.nifi.provenance.WriteAheadProvenanceRepository&lt;/P&gt;&lt;P&gt;# Persistent Provenance Repository Properties&lt;BR /&gt;nifi.provenance.repository.directory.default=./provenance_repository&lt;BR /&gt;nifi.provenance.repository.max.storage.time=30 days&lt;BR /&gt;nifi.provenance.repository.max.storage.size=10 GB&lt;BR /&gt;nifi.provenance.repository.rollover.time=10 mins&lt;BR /&gt;nifi.provenance.repository.rollover.size=100 MB&lt;BR /&gt;nifi.provenance.repository.query.threads=2&lt;BR /&gt;nifi.provenance.repository.index.threads=2&lt;BR /&gt;nifi.provenance.repository.compress.on.rollover=true&lt;BR /&gt;nifi.provenance.repository.always.sync=false&lt;BR /&gt;# Comma-separated list of fields. Fields that are not indexed will not be searchable. Valid fields are:&lt;BR /&gt;# EventType, FlowFileUUID, Filename, TransitURI, ProcessorID, AlternateIdentifierURI, Relationship, Details&lt;BR /&gt;nifi.provenance.repository.indexed.fields=EventType, FlowFileUUID, Filename, ProcessorID, Relationship&lt;BR /&gt;# FlowFile Attributes that should be indexed and made searchable. Some examples to consider are filename, uuid, mime.type&lt;BR /&gt;nifi.provenance.repository.indexed.attributes=&lt;BR /&gt;# Large values for the shard size will result in more Java heap usage when searching the Provenance Repository&lt;BR /&gt;# but should provide better performance&lt;BR /&gt;nifi.provenance.repository.index.shard.size=500 MB&lt;BR /&gt;# Indicates the maximum length that a FlowFile attribute can be when retrieving a Provenance Event from&lt;BR /&gt;# the repository. If the length of any attribute exceeds this value, it will be truncated when the event is retrieved.&lt;BR /&gt;nifi.provenance.repository.max.attribute.length=65536&lt;BR /&gt;nifi.provenance.repository.concurrent.merge.threads=2&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;# Volatile Provenance Respository Properties&lt;BR /&gt;nifi.provenance.repository.buffer.size=100000&lt;/P&gt;&lt;P&gt;# Component and Node Status History Repository&lt;BR /&gt;nifi.components.status.repository.implementation=org.apache.nifi.controller.status.history.VolatileComponentStatusRepository&lt;/P&gt;&lt;P&gt;# Volatile Status History Repository Properties&lt;BR /&gt;nifi.components.status.repository.buffer.size=1440&lt;BR /&gt;nifi.components.status.snapshot.frequency=1 min&lt;/P&gt;&lt;P&gt;# QuestDB Status History Repository Properties&lt;BR /&gt;nifi.status.repository.questdb.persist.node.days=14&lt;BR /&gt;nifi.status.repository.questdb.persist.component.days=3&lt;BR /&gt;nifi.status.repository.questdb.persist.location=./status_repository&lt;/P&gt;&lt;P&gt;# Site to Site properties&lt;BR /&gt;nifi.remote.input.host=nifinode1&lt;BR /&gt;nifi.remote.input.secure=true&lt;BR /&gt;nifi.remote.input.socket.port=10000&lt;BR /&gt;nifi.remote.input.http.enabled=true&lt;/P&gt;&lt;P&gt;nifi.remote.input.socket.port=10000&lt;BR /&gt;nifi.remote.input.http.enabled=true&lt;BR /&gt;nifi.remote.input.http.transaction.ttl=30 sec&lt;BR /&gt;nifi.remote.contents.cache.expiration=30 secs&lt;/P&gt;&lt;P&gt;# web properties #&lt;BR /&gt;#############################################&lt;/P&gt;&lt;P&gt;# For security, NiFi will present the UI on 127.0.0.1 and only be accessible through this loopback interface.&lt;BR /&gt;# Be aware that changing these properties may affect how your instance can be accessed without any restriction.&lt;BR /&gt;# We recommend configuring HTTPS instead. The administrators guide provides instructions on how to do this.&lt;/P&gt;&lt;P&gt;nifi.web.http.host=&lt;BR /&gt;nifi.web.http.port=&lt;BR /&gt;nifi.web.http.network.interface.default=&lt;/P&gt;&lt;P&gt;#############################################&lt;/P&gt;&lt;P&gt;nifi.web.https.host=53.13.138.70&lt;BR /&gt;nifi.web.https.port=8443&lt;BR /&gt;nifi.web.https.network.interface.default=&lt;BR /&gt;nifi.web.https.application.protocols=http/1.1&lt;BR /&gt;nifi.web.jetty.working.directory=./work/jetty&lt;BR /&gt;nifi.web.jetty.threads=200&lt;BR /&gt;nifi.web.max.header.size=16 KB&lt;BR /&gt;nifi.web.proxy.context.path=&lt;BR /&gt;nifi.web.proxy.host=20.61.182.212,20.61.182.212:8443&lt;BR /&gt;nifi.web.max.content.size=&lt;BR /&gt;nifi.web.max.requests.per.second=30000&lt;BR /&gt;nifi.web.max.access.token.requests.per.second=25&lt;BR /&gt;nifi.web.request.timeout=60 secs&lt;BR /&gt;nifi.web.request.ip.whitelist=&lt;BR /&gt;nifi.web.should.send.server.version=true&lt;BR /&gt;nifi.web.request.log.format=%{client}a - %u %t "%r" %s %O "%{Referer}i" "%{User-Agent}i"&lt;/P&gt;&lt;P&gt;# Filter JMX MBeans available through the System Diagnostics REST API&lt;BR /&gt;nifi.web.jmx.metrics.allowed.filter.pattern=&lt;/P&gt;&lt;P&gt;# Include or Exclude TLS Cipher Suites for HTTPS&lt;BR /&gt;nifi.web.https.ciphersuites.include=&lt;BR /&gt;nifi.web.https.ciphersuites.exclude=&lt;/P&gt;&lt;P&gt;# security properties #&lt;BR /&gt;nifi.sensitive.props.key=@Rfs]HjNl=r(z0&amp;amp;ocSsTrrR8rm?/7qMP&lt;BR /&gt;nifi.sensitive.props.key.protected=&lt;BR /&gt;nifi.sensitive.props.algorithm=NIFI_PBKDF2_AES_GCM_256&lt;/P&gt;&lt;P&gt;nifi.sensitive.props.key.protected=&lt;BR /&gt;nifi.sensitive.props.algorithm=NIFI_PBKDF2_AES_GCM_256&lt;BR /&gt;nifi.sensitive.props.additional.keys=&lt;/P&gt;&lt;P&gt;nifi.security.autoreload.enabled=false&lt;BR /&gt;nifi.security.autoreload.interval=10 secs&lt;BR /&gt;nifi.security.keystore=./conf/keystore.p12&lt;BR /&gt;nifi.security.keystoreType=PKCS12&lt;BR /&gt;nifi.security.keystorePasswd=6431841d70fcdad3ba0da5069d579e85&lt;BR /&gt;nifi.security.keyPasswd=6431841d70fcdad3ba0da5069d579e85&lt;BR /&gt;nifi.security.truststore=./conf/truststore.p12&lt;BR /&gt;nifi.security.truststoreType=PKCS12&lt;BR /&gt;nifi.security.truststorePasswd=b6575864ad763da046c01883ae06863c&lt;BR /&gt;nifi.security.user.authorizer=single-user-authorizer&lt;BR /&gt;nifi.security.allow.anonymous.authentication=false&lt;BR /&gt;nifi.security.user.login.identity.provider=single-user-provider&lt;BR /&gt;nifi.security.user.jws.key.rotation.period=PT1H&lt;BR /&gt;nifi.security.ocsp.responder.url=&lt;BR /&gt;nifi.security.ocsp.responder.certificate=&lt;/P&gt;&lt;P&gt;# OpenId Connect SSO Properties #&lt;BR /&gt;nifi.security.user.oidc.discovery.url=&lt;BR /&gt;nifi.security.user.oidc.connect.timeout=5 secs&lt;BR /&gt;nifi.security.user.oidc.read.timeout=5 secs&lt;BR /&gt;nifi.security.user.oidc.client.id=&lt;BR /&gt;nifi.security.user.oidc.client.secret=&lt;BR /&gt;nifi.security.user.oidc.preferred.jwsalgorithm=&lt;BR /&gt;nifi.security.user.oidc.additional.scopes=offline_access&lt;BR /&gt;nifi.security.user.oidc.claim.identifying.user=&lt;BR /&gt;nifi.security.user.oidc.fallback.claims.identifying.user=&lt;BR /&gt;nifi.security.user.oidc.claim.groups=groups&lt;BR /&gt;nifi.security.user.oidc.truststore.strategy=JDK&lt;BR /&gt;nifi.security.user.oidc.token.refresh.window=60 secs&lt;/P&gt;&lt;P&gt;# Apache Knox SSO Properties #&lt;BR /&gt;nifi.security.user.knox.url=&lt;BR /&gt;nifi.security.user.knox.publicKey=&lt;BR /&gt;nifi.security.user.knox.cookieName=hadoop-jwt&lt;BR /&gt;nifi.security.user.knox.audiences=&lt;/P&gt;&lt;P&gt;# SAML Properties #&lt;BR /&gt;nifi.security.user.saml.idp.metadata.url=&lt;BR /&gt;nifi.security.user.saml.sp.entity.id=&lt;BR /&gt;nifi.security.user.saml.identity.attribute.name=&lt;BR /&gt;nifi.security.user.saml.group.attribute.name=&lt;BR /&gt;nifi.security.user.saml.request.signing.enabled=false&lt;/P&gt;&lt;P&gt;nifi.security.user.saml.want.assertions.signed=true&lt;BR /&gt;nifi.security.user.saml.signature.algorithm=&lt;A href="http://www.w3.org/2001/04/xmldsig-more#rsa-sha256" target="_blank" rel="noopener"&gt;http://www.w3.org/2001/04/xmldsig-more#rsa-sha256&lt;/A&gt;&lt;BR /&gt;nifi.security.user.saml.authentication.expiration=12 hours&lt;BR /&gt;nifi.security.user.saml.single.logout.enabled=false&lt;BR /&gt;nifi.security.user.saml.http.client.truststore.strategy=JDK&lt;BR /&gt;nifi.security.user.saml.http.client.connect.timeout=30 secs&lt;BR /&gt;nifi.security.user.saml.http.client.read.timeout=30 secs&lt;/P&gt;&lt;P&gt;# Identity Mapping Properties #&lt;BR /&gt;# These properties allow normalizing user identities such that identities coming from different identity providers&lt;BR /&gt;# (certificates, LDAP, Kerberos) can be treated the same internally in NiFi. The following example demonstrates normalizing&lt;BR /&gt;# DNs from certificates and principals from Kerberos into a common identity string:&lt;BR /&gt;#&lt;BR /&gt;# nifi.security.identity.mapping.pattern.dn=^CN=(.*?), OU=(.*?), O=(.*?), L=(.*?), ST=(.*?), C=(.*?)$&lt;BR /&gt;# nifi.security.identity.mapping.value.dn=$1@$2&lt;BR /&gt;# nifi.security.identity.mapping.transform.dn=NONE&lt;BR /&gt;# nifi.security.identity.mapping.pattern.kerb=^(.*?)/instance@(.*?)$&lt;BR /&gt;# nifi.security.identity.mapping.value.kerb=$1@$2&lt;BR /&gt;# nifi.security.identity.mapping.transform.kerb=UPPER&lt;/P&gt;&lt;P&gt;# Group Mapping Properties #&lt;BR /&gt;# These properties allow normalizing group names coming from external sources like LDAP. The following example&lt;BR /&gt;# lowercases any group name.&lt;BR /&gt;#&lt;BR /&gt;# nifi.security.group.mapping.pattern.anygroup=^(.*)$&lt;BR /&gt;# nifi.security.group.mapping.value.anygroup=$1&lt;BR /&gt;# nifi.security.group.mapping.transform.anygroup=LOWER&lt;/P&gt;&lt;P&gt;# Listener Bootstrap properties #&lt;BR /&gt;# This property defines the port used to listen for communications from NiFi Bootstrap. If this property&lt;BR /&gt;# is missing, empty, or 0, a random ephemeral port is used.&lt;BR /&gt;nifi.listener.bootstrap.port=0&lt;/P&gt;&lt;P&gt;# cluster common properties (all nodes must have same values) #&lt;BR /&gt;nifi.cluster.protocol.heartbeat.interval=5 sec&lt;BR /&gt;nifi.cluster.protocol.heartbeat.missable.max=8&lt;BR /&gt;nifi.cluster.protocol.is.secure=true&lt;/P&gt;&lt;P&gt;# cluster node properties (only configure for cluster nodes) #&lt;BR /&gt;nifi.cluster.is.node=true&lt;BR /&gt;nifi.cluster.node.address=53.13.138.70&lt;BR /&gt;nifi.cluster.node.protocol.port=9991&lt;BR /&gt;nifi.cluster.node.protocol.max.threads=50&lt;BR /&gt;nifi.cluster.node.event.history.size=25&lt;/P&gt;&lt;P&gt;nifi.cluster.node.protocol.max.threads=50&lt;BR /&gt;nifi.cluster.node.event.history.size=25&lt;BR /&gt;nifi.cluster.node.connection.timeout=5 sec&lt;BR /&gt;nifi.cluster.node.read.timeout=5 sec&lt;BR /&gt;nifi.cluster.node.max.concurrent.requests=100&lt;BR /&gt;nifi.cluster.firewall.file=&lt;BR /&gt;nifi.cluster.flow.election.max.wait.time=1 mins&lt;BR /&gt;nifi.cluster.flow.election.max.candidates=&lt;/P&gt;&lt;P&gt;# cluster load balancing properties #&lt;BR /&gt;nifi.cluster.load.balance.host=53.13.138.70&lt;BR /&gt;nifi.cluster.load.balance.port=6342&lt;BR /&gt;nifi.cluster.load.balance.connections.per.node=1&lt;BR /&gt;nifi.cluster.load.balance.max.thread.count=8&lt;BR /&gt;nifi.cluster.load.balance.comms.timeout=30 sec&lt;/P&gt;&lt;P&gt;# zookeeper properties, used for cluster management #&lt;BR /&gt;nifi.zookeeper.connect.string=nifinode1:2181,nifinode2:2181&lt;BR /&gt;nifi.zookeeper.connect.timeout=10 secs&lt;BR /&gt;nifi.zookeeper.session.timeout=10 secs&lt;BR /&gt;nifi.zookeeper.root.node=/nifi&lt;BR /&gt;nifi.zookeeper.client.secure=false&lt;BR /&gt;nifi.zookeeper.security.keystore=&lt;BR /&gt;nifi.zookeeper.security.keystoreType=&lt;BR /&gt;nifi.zookeeper.security.keystorePasswd=&lt;BR /&gt;nifi.zookeeper.security.truststore=&lt;BR /&gt;nifi.zookeeper.security.truststoreType=&lt;BR /&gt;nifi.zookeeper.security.truststorePasswd=&lt;BR /&gt;nifi.zookeeper.jute.maxbuffer=&lt;/P&gt;&lt;P&gt;# Zookeeper properties for the authentication scheme used when creating acls on znodes used for cluster management&lt;BR /&gt;# Values supported for nifi.zookeeper.auth.type are "default", which will apply world/anyone rights on znodes&lt;BR /&gt;# and "sasl" which will give rights to the sasl/kerberos identity used to authenticate the nifi node&lt;BR /&gt;# The identity is determined using the value in nifi.kerberos.service.principal and the removeHostFromPrincipal&lt;BR /&gt;# and removeRealmFromPrincipal values (which should align with the kerberos.removeHostFromPrincipal and kerberos.removeRealmFromPrincipal&lt;BR /&gt;# values configured on the zookeeper server).&lt;BR /&gt;nifi.zookeeper.auth.type=&lt;BR /&gt;nifi.zookeeper.kerberos.removeHostFromPrincipal=&lt;BR /&gt;nifi.zookeeper.kerberos.removeRealmFromPrincipal=&lt;/P&gt;&lt;P&gt;# kerberos #&lt;BR /&gt;nifi.kerberos.krb5.file=&lt;/P&gt;&lt;P&gt;# kerberos service principal #&lt;BR /&gt;nifi.kerberos.service.principal=&lt;BR /&gt;nifi.kerberos.service.keytab.location=&lt;/P&gt;&lt;P&gt;# kerberos spnego principal #&lt;BR /&gt;nifi.kerberos.spnego.principal=&lt;BR /&gt;nifi.kerberos.spnego.keytab.location=&lt;BR /&gt;nifi.kerberos.spnego.authentication.expiration=12 hours&lt;/P&gt;&lt;P&gt;# external properties files for variable registry&lt;BR /&gt;# supports a comma delimited list of file locations&lt;BR /&gt;nifi.variable.registry.properties=&lt;/P&gt;&lt;P&gt;# analytics properties #&lt;BR /&gt;nifi.analytics.predict.enabled=false&lt;BR /&gt;nifi.analytics.predict.interval=3 mins&lt;BR /&gt;nifi.analytics.query.interval=5 mins&lt;BR /&gt;nifi.analytics.connection.model.implementation=org.apache.nifi.controller.status.analytics.models.OrdinaryLeastSquares&lt;BR /&gt;nifi.analytics.connection.model.score.name=rSquared&lt;BR /&gt;nifi.analytics.connection.model.score.threshold=.90&lt;/P&gt;&lt;P&gt;# runtime monitoring properties&lt;BR /&gt;nifi.monitor.long.running.task.schedule=&lt;BR /&gt;nifi.monitor.long.running.task.threshold=&lt;/P&gt;&lt;P&gt;# Enable automatic diagnostic at shutdown.&lt;BR /&gt;nifi.diagnostics.on.shutdown.enabled=false&lt;/P&gt;&lt;P&gt;# Include verbose diagnostic information.&lt;BR /&gt;nifi.diagnostics.on.shutdown.verbose=false&lt;/P&gt;&lt;P&gt;# The location of the diagnostics folder.&lt;BR /&gt;nifi.diagnostics.on.shutdown.directory=./diagnostics&lt;/P&gt;&lt;P&gt;# The maximum number of files permitted in the directory. If the limit is exceeded, the oldest files are deleted.&lt;BR /&gt;nifi.diagnostics.on.shutdown.max.filecount=10&lt;/P&gt;&lt;P&gt;# The diagnostics folder's maximum permitted size in bytes. If the limit is exceeded, the oldest files are deleted.&lt;BR /&gt;nifi.diagnostics.on.shutdown.max.directory.size=10 MB&lt;/P&gt;&lt;P&gt;# Performance tracking properties&lt;BR /&gt;## Specifies what percentage of the time we should track the amount of time processors are using CPU, reading from/writing to content repo, etc.&lt;BR /&gt;## This can be useful to understand which components are the most expensive and to understand where system bottlenecks may be occurring.&lt;BR /&gt;## The value must be in the range of 0 (inclusive) to 100 (inclusive). A larger value will produce more accurate results, while a smaller value may be&lt;BR /&gt;## less expensive to compute.&lt;BR /&gt;## Results can be obtained by running "nifi.sh diagnostics &amp;lt;filename&amp;gt;" and then inspecting the produced file.&lt;BR /&gt;nifi.performance.tracking.percentage=0&lt;/P&gt;&lt;P&gt;# NAR Provider Properties #&lt;BR /&gt;# These properties allow configuring one or more NAR providers. A NAR provider retrieves NARs from an external source&lt;BR /&gt;# and copies them to the directory specified by nifi.nar.library.autoload.directory.&lt;BR /&gt;#&lt;BR /&gt;# Each NAR provider property follows the format:&lt;BR /&gt;# nifi.nar.library.provider.&amp;lt;identifier&amp;gt;.&amp;lt;property-name&amp;gt;&lt;BR /&gt;#&lt;BR /&gt;# Each NAR provider must have at least one property named "implementation".&lt;BR /&gt;#&lt;BR /&gt;# Example HDFS NAR Provider:&lt;BR /&gt;# nifi.nar.library.provider.hdfs.implementation=org.apache.nifi.flow.resource.hadoop.HDFSExternalResourceProvider&lt;BR /&gt;# nifi.nar.library.provider.hdfs.resources=/path/to/core-site.xml,/path/to/hdfs-site.xml&lt;BR /&gt;# nifi.nar.library.provider.hdfs.storage.location=hdfs://hdfs-location&lt;BR /&gt;# nifi.nar.library.provider.hdfs.source.directory=/nars&lt;BR /&gt;# nifi.nar.library.provider.hdfs.kerberos.principal=nifi@NIFI.COM&lt;BR /&gt;# nifi.nar.library.provider.hdfs.kerberos.keytab=/path/to/nifi.keytab&lt;BR /&gt;# nifi.nar.library.provider.hdfs.kerberos.password=&lt;BR /&gt;#&lt;BR /&gt;# Example NiFi Registry NAR Provider:&lt;BR /&gt;# nifi.nar.library.provider.nifi-registry.implementation=org.apache.nifi.registry.extension.NiFiRegistryNarProvider&lt;BR /&gt;# nifi.nar.library.provider.nifi-registry.url=&lt;A href="http://localhost:18080" target="_blank" rel="noopener"&gt;http://localhost:18080&lt;/A&gt;&lt;BR /&gt;~/&lt;/P&gt;&lt;P&gt;****************************************************************************************************&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;providing state-managment.xml&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;--&amp;gt;&lt;/P&gt;&lt;P&gt;&amp;lt;/html&amp;gt;&lt;BR /&gt;&amp;lt;local-provider&amp;gt;&lt;BR /&gt;&amp;lt;id&amp;gt;local-provider&amp;lt;/id&amp;gt;&lt;BR /&gt;&amp;lt;class&amp;gt;org.apache.nifi.controller.state.providers.local.WriteAheadLocalStateProvider&amp;lt;/class&amp;gt;&lt;BR /&gt;&amp;lt;property name="Directory"&amp;gt;./state/local&amp;lt;/property&amp;gt;&lt;BR /&gt;&amp;lt;property name="Always Sync"&amp;gt;false&amp;lt;/property&amp;gt;&lt;BR /&gt;&amp;lt;property name="Partitions"&amp;gt;16&amp;lt;/property&amp;gt;&lt;BR /&gt;&amp;lt;property name="Checkpoint Interval"&amp;gt;2 mins&amp;lt;/property&amp;gt;&lt;BR /&gt;&amp;lt;/local-provider&amp;gt;&lt;STRONG&gt;&lt;BR /&gt;&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&amp;lt;cluster-provider&amp;gt;&lt;BR /&gt;&amp;lt;id&amp;gt;zk-provider&amp;lt;/id&amp;gt;&lt;BR /&gt;&amp;lt;class&amp;gt;org.apache.nifi.controller.state.providers.zookeeper.ZooKeeperStateProvider&amp;lt;/class&amp;gt;&lt;BR /&gt;&amp;lt;property name="Connect String"&amp;gt;nifinode1:2188, nifinode2:2188&amp;lt;/property&amp;gt;&lt;BR /&gt;&amp;lt;property name="Root Node"&amp;gt;/nifi&amp;lt;/property&amp;gt;&lt;BR /&gt;&amp;lt;property name="Session Timeout"&amp;gt;10 seconds&amp;lt;/property&amp;gt;&lt;BR /&gt;&amp;lt;property name="Access Control"&amp;gt;Open&amp;lt;/property&amp;gt;&lt;BR /&gt;&amp;lt;/cluster-provider&amp;gt;&lt;/P&gt;&lt;P&gt;******************************************************************************************************&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;Attaching the zokeeper properties&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;server.1=nifinode1:2888:3888;2181&lt;BR /&gt;server.2=nifinode2:2888:3888;2181&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Request you to please check and update what i am missing, i am a new to an NIFI, so getting through many issues.&lt;/P&gt;&lt;P&gt;***********************************************************************************************&lt;/P&gt;&lt;P&gt;Also i getting login screen from the loadbalancer ip but unable to login with the generated username and password&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="vg27_0-1729613638857.png" style="width: 400px;"&gt;&lt;img src="https://community.cloudera.com/t5/image/serverpage/image-id/42308iC391DEC7095750AF/image-size/medium?v=v2&amp;amp;px=400" role="button" title="vg27_0-1729613638857.png" alt="vg27_0-1729613638857.png" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;P&gt;can u please guide what will be the username here, we are not using any certficate currently&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 22 Oct 2024 16:14:27 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Support-Questions/Nifi-Unable-to-elect-cluster-coordinator/m-p/395748#M249013</guid>
      <dc:creator>vg27</dc:creator>
      <dc:date>2024-10-22T16:14:27Z</dc:date>
    </item>
    <item>
      <title>Re: Nifi : Unable to elect cluster coordinator</title>
      <link>https://community.cloudera.com/t5/Support-Questions/Nifi-Unable-to-elect-cluster-coordinator/m-p/395803#M249029</link>
      <description>&lt;P&gt;&lt;a href="https://community.cloudera.com/t5/user/viewprofilepage/user-id/80381"&gt;@SAMSAL&lt;/a&gt;&amp;nbsp;&lt;a href="https://community.cloudera.com/t5/user/viewprofilepage/user-id/11191"&gt;@araujo&lt;/a&gt;&amp;nbsp;, can you please check and help us its getting bloked for our testing&lt;/P&gt;</description>
      <pubDate>Wed, 23 Oct 2024 09:13:06 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Support-Questions/Nifi-Unable-to-elect-cluster-coordinator/m-p/395803#M249029</guid>
      <dc:creator>vg27</dc:creator>
      <dc:date>2024-10-23T09:13:06Z</dc:date>
    </item>
    <item>
      <title>Re: Nifi : Unable to elect cluster coordinator</title>
      <link>https://community.cloudera.com/t5/Support-Questions/Nifi-Unable-to-elect-cluster-coordinator/m-p/395819#M249033</link>
      <description>&lt;P&gt;&lt;a href="https://community.cloudera.com/t5/user/viewprofilepage/user-id/118267"&gt;@vg27&lt;/a&gt;&amp;nbsp;&lt;BR /&gt;&lt;BR /&gt;If you have a support contract with Cloudera, you could open a support case where someone could connect directly with you and assist you through your many issues.&lt;BR /&gt;&lt;BR /&gt;------&lt;BR /&gt;1. As i have shared before, the Single-User providers are not designed with the intent of use in a NiFi clustered environment.&amp;nbsp; They should only be used for standalone NiFi evaluation purposes.&amp;nbsp; Once you start to get in to the more involved cluster based deployments, you need to use different providers for authentication and authorization.&amp;nbsp; When using the single-user-provider for authentication, each node can create different credentials which will not work in a cluster environment.&amp;nbsp; &amp;nbsp;&lt;BR /&gt;&lt;BR /&gt;For login based authentication, you should be using LDAP/AD (ldap-provider) or Kerberos (Kerberos-provider).&amp;nbsp;&lt;BR /&gt;&lt;BR /&gt;For authorization, you should be using the managed authorizer.&amp;nbsp;&lt;BR /&gt;&lt;BR /&gt;------&lt;/P&gt;&lt;P&gt;2. Are you still using your own generated keystore and truststore with your own created private and public certificates?&amp;nbsp; Using the NiFi auto-generated keystore and truststore will also not support clustering well as each node will not have a common certificate authority.&amp;nbsp;&lt;BR /&gt;&lt;BR /&gt;-----&lt;BR /&gt;3. The "&lt;SPAN&gt;org.apache.zookeeper.KeeperException$ConnectionLossException: KeeperErrorCode = ConnectionLoss" exception is an issue with with Zookeeper (ZK) Quorum.&amp;nbsp; This error can happen if both you nodes are not fully up at time of exception and may also happen because you do not have proper quorum with your ZK.&amp;nbsp; Quorum consists of and odd number of ZK hosts with min 3.&amp;nbsp; Strongly encourage the use of an external ZK since anytime one of your nodes goes down, you'll lose access to both nodes.&lt;BR /&gt;&lt;BR /&gt;-----&lt;BR /&gt;4. You are using an external https Load Balancer (LB) which means that sticky sessions (session affinity) must be setup since the user token issues when you login is only valid for use with the node that issued it.&amp;nbsp; So if your LB directs you to node 1 that presents you with login UI, you enter credentials obtaining a user token from node 1, and your LB then redirects to node 2 to load UI, it will fail authentication on node 2 because the request includes the token only good for node 1.&amp;nbsp;&lt;BR /&gt;&lt;BR /&gt;-----&lt;BR /&gt;5. I see you are using a mix of hostnames and IP addresses in your NiFi configurations, so make sure that the node certificates include both as SAN entries to avoid issues.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;-----&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Please help our community thrive. If you found&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;STRONG&gt;any&lt;/STRONG&gt;&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;of the suggestions/solutions provided helped you with solving your issue or answering your question, please take a moment to login and click "&lt;SPAN&gt;&lt;EM&gt;&lt;STRONG&gt;&lt;FONT color="#FF0000"&gt;Accept as Solution&lt;/FONT&gt;&lt;/STRONG&gt;&lt;/EM&gt;" on&amp;nbsp;&lt;STRONG&gt;one or more&lt;/STRONG&gt;&amp;nbsp;of them that helped.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;Thank you,&lt;BR /&gt;Matt&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Wed, 23 Oct 2024 13:02:18 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Support-Questions/Nifi-Unable-to-elect-cluster-coordinator/m-p/395819#M249033</guid>
      <dc:creator>MattWho</dc:creator>
      <dc:date>2024-10-23T13:02:18Z</dc:date>
    </item>
    <item>
      <title>Re: Nifi : Unable to elect cluster coordinator</title>
      <link>https://community.cloudera.com/t5/Support-Questions/Nifi-Unable-to-elect-cluster-coordinator/m-p/395831#M249041</link>
      <description>&lt;P&gt;HI&amp;nbsp;&lt;a href="https://community.cloudera.com/t5/user/viewprofilepage/user-id/35454"&gt;@MattWho&lt;/a&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;can you provide how to get the support subscription, i am unable to find it in online.&lt;/P&gt;</description>
      <pubDate>Wed, 23 Oct 2024 15:16:03 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Support-Questions/Nifi-Unable-to-elect-cluster-coordinator/m-p/395831#M249041</guid>
      <dc:creator>vg27</dc:creator>
      <dc:date>2024-10-23T15:16:03Z</dc:date>
    </item>
    <item>
      <title>Re: Nifi : Unable to elect cluster coordinator</title>
      <link>https://community.cloudera.com/t5/Support-Questions/Nifi-Unable-to-elect-cluster-coordinator/m-p/395859#M249046</link>
      <description>&lt;P&gt;&lt;a href="https://community.cloudera.com/t5/user/viewprofilepage/user-id/118267"&gt;@vg27&lt;/a&gt;&amp;nbsp;I have submitted your information to the team, they will be contacting you with the following steps, thanks!&lt;/P&gt;</description>
      <pubDate>Wed, 23 Oct 2024 18:53:04 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Support-Questions/Nifi-Unable-to-elect-cluster-coordinator/m-p/395859#M249046</guid>
      <dc:creator>DianaTorres</dc:creator>
      <dc:date>2024-10-23T18:53:04Z</dc:date>
    </item>
  </channel>
</rss>

