markap14 commented on PR #6779: URL: https://github.com/apache/nifi/pull/6779#issuecomment-1355512778
Thanks @exceptionfactory . Pulled the latest, rebuilt everything, rebuilt the docker image. Interestingly, it no longer worked. I got errors on startup telling me that the URI was invalid when calling `leaderElectionCommandProvider.findLeader(roleName);` (line 197 of KubernetesLeaderElectionManager) because the URI ended in "/Cluster Coordinator". So I updated that code to get the `roleId` for the `roleName` and provide that. That addressed the issue. It was now registering for the role properly. Unfortunately, though, I still ran into the exact same issue. When I disconnected and reconnected a node, it gave the same stack trace, failing to release the lease because it was modified. This then caused the same issue, with both nodes thinking they are the leader. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
