You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@nifi.apache.org by "Pierre Villard (Jira)" <ji...@apache.org> on 2026/01/05 10:36:08 UTC
[jira] [Resolved] (NIFI-7793) Time shift and embedded Zookeeper
[ https://issues.apache.org/jira/browse/NIFI-7793?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Pierre Villard resolved NIFI-7793.
----------------------------------
Resolution: Feedback Received
Apache NiFi 1.x is no longer maintained and no new release is planned on the 1.x release line. Marking as resolved as part of a cleanup operation. Please open a new one with an updated description if this is still relevant for NiFi 2.x.
> Time shift and embedded Zookeeper
> ---------------------------------
>
> Key: NIFI-7793
> URL: https://issues.apache.org/jira/browse/NIFI-7793
> Project: Apache NiFi
> Issue Type: Bug
> Components: Documentation & Website, NiFi Stateless
> Affects Versions: 1.9.2
> Reporter: Maria Saenz
> Priority: Minor
>
> Dear teams
> It was recently the time change in Chile. My cluster works with an embedded zookeper and with three nodes.
> When the time change was generated, the cluster had the processes stopped but it was running. After the time change I restarted it and a node did not return, it did not communicate with the other two that were started and forming the cluster.
> The solution to this problem was to raise the nodes one by one in an odd order. Once all the nodes are disconnected, the nodes are restarted again forming the cluster mode.
> Do you have an idea why that behavior?
--
This message was sent by Atlassian Jira
(v8.20.10#820010)