NIFI-2566: Refactoring to improve robustness of cluster#866
NIFI-2566: Refactoring to improve robustness of cluster#866markap14 wants to merge 4 commits intoapache:masterfrom
Conversation
… responsible for determining who is the Cluster Coordinator
…onnectionStatus; use LeaderElectionManager to determine roles instead
|
|
||
| final boolean updated = clusterCoordinator.resetNodeStatus(updatedStatus, updateId == null ? -1L : updateId); | ||
| if (updated) { | ||
| // TODO - REMOVE THE ASTERISKS |
There was a problem hiding this comment.
Lingering Todo, can it be removed?
…luster topology, cluster coordinator will provide updated information back to the nodes
|
@markap14, I'm having trouble running a standalone instance with this PR. I get the at I can't start the FlowController due to (very long message, took the end):
|
|
@JPercivall I pushed an update that should address this issue. |
…ng by creating a standalone-instance version of the Leader Election Manager. Also added Controller Service enabled/disabled state to fingerprint rather than attempting to update the state when joining the cluster, as the implementation was incorrect and the correct implementation will be a rather significant effort that doesn't have to happen for 1.0.0 release
|
+1 Visually verified code, and did a contrib check build rebased to master. In a 3 node secure cluster did all sorts of tests involving connecting, disconnecting, restarting, and starting/stopping components. All behaved as expected. Thanks @markap14, I will merge it in. Edit: Also started up a standealone instance to verify things didn't get messed up there. |
2 participants
No description provided.