This is an automated email from the ASF dual-hosted git repository.
exceptionfactory pushed a commit to branch main
in repository https://gitbox.apache.org/repos/asf/nifi.git
The following commit(s) were added to refs/heads/main by this push:
new 115d5740f8 NIFI-13009 Update documentation and UI for Disconnected
Node changes (#10354)
115d5740f8 is described below
commit 115d5740f8c21329ba915557ed39415bebf03fdc
Author: NissimShiman <[email protected]>
AuthorDate: Tue Sep 30 17:18:50 2025 -0400
NIFI-13009 Update documentation and UI for Disconnected Node changes
(#10354)
Signed-off-by: David Handermann <[email protected]>
---
nifi-docs/src/main/asciidoc/administration-guide.adoc | 6 +++++-
.../nifi/src/app/state/cluster-summary/cluster-summary.effects.ts | 2 +-
2 files changed, 6 insertions(+), 2 deletions(-)
diff --git a/nifi-docs/src/main/asciidoc/administration-guide.adoc
b/nifi-docs/src/main/asciidoc/administration-guide.adoc
index 1168d57314..75e2210cc5 100644
--- a/nifi-docs/src/main/asciidoc/administration-guide.adoc
+++ b/nifi-docs/src/main/asciidoc/administration-guide.adoc
@@ -1995,7 +1995,11 @@ nodes and waits for each node to respond, indicating
that it has made the change
==== Disconnect Nodes
-A DFM may manually disconnect a node from the cluster. A node may also become
disconnected for other reasons, such as due to a lack of heartbeat. The Cluster
Coordinator will show a bulletin on the User Interface when a node is
disconnected. The DFM will not be able to make any changes to the dataflow
until the issue of the disconnected node is resolved. The DFM or the
Administrator will need to troubleshoot the issue with the node and resolve it
before any new changes can be made to the [...]
+A DFM may manually disconnect a node from the cluster. A node may also become
disconnected for other reasons, such as due to a lack of heartbeat. The Cluster
Coordinator will show a bulletin on the User Interface when a node is
disconnected. Until the issue with the node is resolved, the DFM will have
limited ability to make changes to the remaining cluster's dataflow. Changing
component state or adding a component is allowed, but removing a component is
not.
+
+A node that was disconnected maybe fully working. This may happen for a few
reasons, for example when the node is unable to communicate with the Cluster
Coordinator due to network problems.
+
+It should be noted that a disconnected node's dataflow is allowed to be
changed. Any changes should be done with caution, however, as they will be
reverted when the node is re-attached to the cluster. In addition, if
reverting the changes will cause a loss of data then it will not be allowed to
rejoin the cluster. This can occur if a new dataflow has since been made on
the disconnected node.
To manually disconnect a node, select the "Disconnect" icon
(image:iconDisconnect.png["Disconnect Icon"]) from the node's row.
diff --git
a/nifi-frontend/src/main/frontend/apps/nifi/src/app/state/cluster-summary/cluster-summary.effects.ts
b/nifi-frontend/src/main/frontend/apps/nifi/src/app/state/cluster-summary/cluster-summary.effects.ts
index 3974441d5b..1e0a584743 100644
---
a/nifi-frontend/src/main/frontend/apps/nifi/src/app/state/cluster-summary/cluster-summary.effects.ts
+++
b/nifi-frontend/src/main/frontend/apps/nifi/src/app/state/cluster-summary/cluster-summary.effects.ts
@@ -101,7 +101,7 @@ export class ClusterSummaryEffects {
tap(({ connectedToCluster }) => {
const message = connectedToCluster
? 'This node just joined the cluster. Any
modifications to the data flow made here will replicate across the cluster.'
- : 'This node is currently not connected to the
cluster. Any modifications to the data flow made here will not replicate across
the cluster.';
+ : 'This node is currently not connected to the
cluster. Any modifications to the data flow made here will not replicate across
the cluster and will revert upon rejoining.';
const dialogReference = this.dialog.open(OkDialog, {
...MEDIUM_DIALOG,
