Excellent! Glad it's all working now. And thanks for the follow-up to let us
know!
-Mark
> On Apr 12, 2017, at 11:30 AM, Mark Bean wrote:
>
> Mark,
>
> I believe you're right. Yesterday, I corrected a typo in the
> nifi.properties file related to the FQDN name. I thought it was only the
> sit
Mark,
I believe you're right. Yesterday, I corrected a typo in the
nifi.properties file related to the FQDN name. I thought it was only the
site-to-site property (nifi.remote.input.host). However, when I
intentionally introduced a typo to one of the three ZK servers in the
nifi.zookeeper.connect.s
Mark,
I haven't seen this behavior personally, so I can't be sure why exactly it
would change state
to SUSPENDED and not then re-connect. In your nifi.properties, do you have the
"nifi.zookeeper.connect.string" property setup to point to all 3 of the nodes,
also? If so, it should
be able to con
To echo Max... I had some similar issues using the embedded Zookeeper. I
switched to my cluster Zookeeper and have not seen this issue since.
On Tue, Apr 11, 2017 at 11:37 AM, Mark Bean wrote:
> Ok, will keep the standalone ZooKeeper in mind.
>
> Back to the original issue, any idea why ZooKeepe
Ok, will keep the standalone ZooKeeper in mind.
Back to the original issue, any idea why ZooKeeper went to a PENDING state
making the cluster unavailable?
On Tue, Apr 11, 2017 at 2:10 PM, Mark Payne wrote:
> Mark,
>
> Yes, 2 out of 3 should be sufficient. For testing purposes, a single
> zooke
Mark,
Yes, 2 out of 3 should be sufficient. For testing purposes, a single zookeeper
instance
is fine, as well. For production, I would not actually recommend using an
embedded
ZooKeeper at all and instead use a standalone ZooKeeper. ZooKeeper tends not to
be
very happy when running on a box on
All 3 nodes are running embedded ZooKeeper. And, the Admin Guide states
"ZooKeeper requires a majority of nodes be active in order to function".
So, I assumed 2/3 being active was ok. Perhaps not.
Related: can a Cluster be setup with only 1 ZooKeeper node? Clearly, in
production, one would not wan
Mark,
Are all of your nodes running an embedded ZooKeeper, or only 1 or 2 of them?
Thanks
-Mark
> On Apr 11, 2017, at 1:19 PM, Mark Bean wrote:
>
> I have a 3-node Cluster with each Node hosting the embedded zookeeper. When
> one Node is shutdown (and the Node is not the Cluster Coordinator),
I have a 3-node Cluster with each Node hosting the embedded zookeeper. When
one Node is shutdown (and the Node is not the Cluster Coordinator), the
Cluster becomes unavailable. The UI indicates "Action cannot be performed
because there is currently no Cluster Coordinator elected. The request
should
