[
https://issues.apache.org/jira/browse/NIFI-9559?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17538773#comment-17538773
]
Shawn Weeks commented on NIFI-9559:
-----------------------------------
I was able to partially reproduce the behavior overnight. By setting
minSessionTimeout and maxSessionTimeout to a low value like 500 and 1000 and
introducing delays and packet loss with "tc" in Linux I eventually ended up
with a NiFi cluster without a cluster coordinator being elected and it did not
re-elect one when I switched zookeeper back to it's default timeouts and
removed the delays. It's possible I've ran into a different issue though since
it's not printing the session expired error over and over again.
> Zookeeper Client Can't Reconnect - Session timeout has elapsed while SUSPENDED
> ------------------------------------------------------------------------------
>
> Key: NIFI-9559
> URL: https://issues.apache.org/jira/browse/NIFI-9559
> Project: Apache NiFi
> Issue Type: Bug
> Reporter: Shawn Weeks
> Assignee: Nathan Gough
> Priority: Minor
> Attachments: nifi_and_zookeeper_logs.txt, nifi_error.log
>
>
> After a loss of connection to Zookeeper a NiFi node never successfully
> reconnects to the Zookeeper or the Cluster and instead returns errors about
> no Cluster Coordinator and a Session timeout has elapsed while SUSPENDED
> repeatedly until you restart NiFi.
> The error described is the same one at
> https://issues.apache.org/jira/browse/CURATOR-405 however that patch has been
> in NiFi for several versions now.
> NiFi version is 1.15.3 and Zookeeper 3.6.3
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
