[jira] [Updated] (NIFI-5585) Decommision Nodes from Cluster
[
https://issues.apache.org/jira/browse/NIFI-5585?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jeff Storck updated NIFI-5585:
--
Description:
Allow a node in the cluster to be decommissioned, rebalancing flowfiles on the
node to be decommissioned to the other active nodes. This work depends on
NIFI-5516.
Similar to the client sending PUT request a DISCONNECTING message to
cluster/nodes/\{id}, an OFFLOADING message can be sent as a PUT request to the
same URI to initiate an OFFLOAD for a DISCONNECTED node. The OFFLOADING request
will be idempotent.
Only nodes that are DISCONNECTED can be transitioned to the OFFLOADING state.
After the node completes offloading, it will transition to the OFFLOADED state.
OFFLOADED nodes can be reconnected to the cluster by issuing a connection
request via the UI/CLI, or restarting NiFi on the node.
The steps to decommission a node and remove it from the cluster are:
# Send request to disconnect the node
# Once disconnect completes, send request to offload the node.
# Once offload completes, send request to delete node.
# Once the delete request has finished, the NiFi service on the host can be
stopped/removed.
When an error occurs and the node can not complete offloading, the user can:
# Send request to delete the node from the cluster
# Diagnose why the node had issues with the offload (out of memory, no network
connection, etc) and address the issue
# Restart NiFi on the node to so that it will reconnect to the cluster
# Go through the steps to decommission a node
Toolkit CLI commands for retrieving a list of nodes and
connecting/disconnecting/offloading/deleting nodes have been added.
was:
Allow a node in the cluster to be decommissioned, rebalancing flowfiles on the
node to be decommissioned to the other active nodes. This work depends on
NIFI-5516.
Similar to the client sending PUT request a DISCONNECTING message to
cluster/nodes/\{id}, a DECOMMISSIONING message can be sent as a PUT request to
the same URI to initiate a DECOMMISSION for a DISCONNECTED node. The
DECOMMISSIONING request will be idempotent.
The steps to decommission a node and remove it from the cluster are:
# Send request to disconnect the node
# Once disconnect completes, send request to decommission the node.
# Once decommission completes, send request to delete node.
When an error occurs and the node can not complete decommissioning, the user
can:
# Send request to delete the node from the cluster
# Diagnose why the node had issues with the decommission (out of memory, no
network connection, etc) and address the issue
# Restart NiFi on the node to so that it will reconnect to the cluster
# Go through the steps to decommission and remove a node
Toolkit CLI commands for retrieving a list of nodes and
disconnecting/decommissioning/deleting nodes have been added.
> Decommision Nodes from Cluster
> --
>
> Key: NIFI-5585
> URL: https://issues.apache.org/jira/browse/NIFI-5585
> Project: Apache NiFi
> Issue Type: Improvement
> Components: Core Framework
>Affects Versions: 1.7.1
>Reporter: Jeff Storck
>Assignee: Jeff Storck
>Priority: Major
>
> Allow a node in the cluster to be decommissioned, rebalancing flowfiles on
> the node to be decommissioned to the other active nodes. This work depends
> on NIFI-5516.
> Similar to the client sending PUT request a DISCONNECTING message to
> cluster/nodes/\{id}, an OFFLOADING message can be sent as a PUT request to
> the same URI to initiate an OFFLOAD for a DISCONNECTED node. The OFFLOADING
> request will be idempotent.
> Only nodes that are DISCONNECTED can be transitioned to the OFFLOADING state.
> After the node completes offloading, it will transition to the OFFLOADED
> state.
> OFFLOADED nodes can be reconnected to the cluster by issuing a connection
> request via the UI/CLI, or restarting NiFi on the node.
> The steps to decommission a node and remove it from the cluster are:
> # Send request to disconnect the node
> # Once disconnect completes, send request to offload the node.
> # Once offload completes, send request to delete node.
> # Once the delete request has finished, the NiFi service on the host can be
> stopped/removed.
> When an error occurs and the node can not complete offloading, the user can:
> # Send request to delete the node from the cluster
> # Diagnose why the node had issues with the offload (out of memory, no
> network connection, etc) and address the issue
> # Restart NiFi on the node to so that it will reconnect to the cluster
> # Go through the steps to decommission a node
> Toolkit CLI commands for retrieving a list of nodes and
> connecting/disconnecting/offloading/deleting nodes have been added.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (NIFI-5585) Decommision Nodes from Cluster
[
https://issues.apache.org/jira/browse/NIFI-5585?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jeff Storck updated NIFI-5585:
--
Description:
Allow a node in the cluster to be decommissioned, rebalancing flowfiles on the
node to be decommissioned to the other active nodes. This work depends on
NIFI-5516.
Similar to the client sending PUT request a DISCONNECTING message to
cluster/nodes/\{id}, a DECOMMISSIONING message can be sent as a PUT request to
the same URI to initiate a DECOMMISSION for a DISCONNECTED node. The
DECOMMISSIONING request will be idempotent.
The steps to decommission a node and remove it from the cluster are:
# Send request to disconnect the node
# Once disconnect completes, send request to decommission the node.
# Once decommission completes, send request to delete node.
When an error occurs and the node can not complete decommissioning, the user
can:
# Send request to delete the node from the cluster
# Diagnose why the node had issues with the decommission (out of memory, no
network connection, etc) and address the issue
# Restart NiFi on the node to so that it will reconnect to the cluster
# Go through the steps to decommission and remove a node
Toolkit CLI commands for retrieving a list of nodes and
disconnecting/decommissioning/deleting nodes have been added.
was:
Allow a node in the cluster to be decommissioned, rebalancing flowfiles on the
node to be decommissioned to the other active nodes. This work depends on
NIFI-5516.
Similar to the client sending PUT request a DISCONNECTING message to
cluster/nodes/\{id}, a DECOMMISSIONING message can be sent as a PUT request to
the same URI to initiate a DECOMMISSION for a DISCONNECTED node. The
DECOMMISSIONING request will be idempotent.
The steps to decommission a node and remove it from the cluster are:
# Send request to disconnect the node
# Once disconnect completes, send request to decommission the node.
# Once decommission completes, send request to delete node.
When an error occurs and the node can not complete decommissioning, the user
can:
# Send request to delete the node from the cluster
# Diagnose why the node had issues with the decommission (out of memory, no
network connection, etc) and address the issue
# Restart NiFi on the node to so that it will reconnect to the cluster
# Go through the steps to decommission and remove a node
> Decommision Nodes from Cluster
> --
>
> Key: NIFI-5585
> URL: https://issues.apache.org/jira/browse/NIFI-5585
> Project: Apache NiFi
> Issue Type: Improvement
> Components: Core Framework
>Affects Versions: 1.7.1
>Reporter: Jeff Storck
>Assignee: Jeff Storck
>Priority: Major
>
> Allow a node in the cluster to be decommissioned, rebalancing flowfiles on
> the node to be decommissioned to the other active nodes. This work depends
> on NIFI-5516.
> Similar to the client sending PUT request a DISCONNECTING message to
> cluster/nodes/\{id}, a DECOMMISSIONING message can be sent as a PUT request
> to the same URI to initiate a DECOMMISSION for a DISCONNECTED node. The
> DECOMMISSIONING request will be idempotent.
> The steps to decommission a node and remove it from the cluster are:
> # Send request to disconnect the node
> # Once disconnect completes, send request to decommission the node.
> # Once decommission completes, send request to delete node.
> When an error occurs and the node can not complete decommissioning, the user
> can:
> # Send request to delete the node from the cluster
> # Diagnose why the node had issues with the decommission (out of memory, no
> network connection, etc) and address the issue
> # Restart NiFi on the node to so that it will reconnect to the cluster
> # Go through the steps to decommission and remove a node
> Toolkit CLI commands for retrieving a list of nodes and
> disconnecting/decommissioning/deleting nodes have been added.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (NIFI-5585) Decommision Nodes from Cluster
[
https://issues.apache.org/jira/browse/NIFI-5585?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jeff Storck updated NIFI-5585:
--
Status: Patch Available (was: In Progress)
WIP Apache NiFi [PR 3010|https://github.com/apache/nifi/pull/3010]
> Decommision Nodes from Cluster
> --
>
> Key: NIFI-5585
> URL: https://issues.apache.org/jira/browse/NIFI-5585
> Project: Apache NiFi
> Issue Type: Improvement
> Components: Core Framework
>Affects Versions: 1.7.1
>Reporter: Jeff Storck
>Assignee: Jeff Storck
>Priority: Major
>
> Allow a node in the cluster to be decommissioned, rebalancing flowfiles on
> the node to be decommissioned to the other active nodes. This work depends
> on NIFI-5516.
> Similar to the client sending PUT request a DISCONNECTING message to
> cluster/nodes/\{id}, a DECOMMISSIONING message can be sent as a PUT request
> to the same URI to initiate a DECOMMISSION for a DISCONNECTED node. The
> DECOMMISSIONING request will be idempotent.
> The steps to decommission a node and remove it from the cluster are:
> # Send request to disconnect the node
> # Once disconnect completes, send request to decommission the node.
> # Once decommission completes, send request to delete node.
> When an error occurs and the node can not complete decommissioning, the user
> can:
> # Send request to delete the node from the cluster
> # Diagnose why the node had issues with the decommission (out of memory, no
> network connection, etc) and address the issue
> # Restart NiFi on the node to so that it will reconnect to the cluster
> # Go through the steps to decommission and remove a node
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (NIFI-5585) Decommision Nodes from Cluster
[
https://issues.apache.org/jira/browse/NIFI-5585?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jeff Storck updated NIFI-5585:
--
Description:
Allow a node in the cluster to be decommissioned, rebalancing flowfiles on the
node to be decommissioned to the other active nodes. This work depends on
NIFI-5516.
Similar to the client sending PUT request a DISCONNECTING message to
cluster/nodes/\{id}, a DECOMMISSIONING message can be sent as a PUT request to
the same URI to initiate a DECOMMISSION for a DISCONNECTED node. The
DECOMMISSIONING request will be idempotent.
The steps to decommission a node and remove it from the cluster are:
# Send request to disconnect the node
# Once disconnect completes, send request to decommission the node.
# Once decommission completes, send request to delete node.
When an error occurs and the node can not complete decommissioning, the user
can:
# Send request to delete the node from the cluster
# Diagnose why the node had issues with the decommission (out of memory, no
network connection, etc) and address the issue
# Restart NiFi on the node to so that it will reconnect to the cluster
# Go through the steps to decommission and remove a node
was:Allow a node in the cluster to be decommissioned, rebalancing flowfiles
on the node to be decommissioned to the other active nodes. This work depends
on NIFI-5516.
> Decommision Nodes from Cluster
> --
>
> Key: NIFI-5585
> URL: https://issues.apache.org/jira/browse/NIFI-5585
> Project: Apache NiFi
> Issue Type: Improvement
> Components: Core Framework
>Affects Versions: 1.7.1
>Reporter: Jeff Storck
>Assignee: Jeff Storck
>Priority: Major
>
> Allow a node in the cluster to be decommissioned, rebalancing flowfiles on
> the node to be decommissioned to the other active nodes. This work depends
> on NIFI-5516.
> Similar to the client sending PUT request a DISCONNECTING message to
> cluster/nodes/\{id}, a DECOMMISSIONING message can be sent as a PUT request
> to the same URI to initiate a DECOMMISSION for a DISCONNECTED node. The
> DECOMMISSIONING request will be idempotent.
> The steps to decommission a node and remove it from the cluster are:
> # Send request to disconnect the node
> # Once disconnect completes, send request to decommission the node.
> # Once decommission completes, send request to delete node.
> When an error occurs and the node can not complete decommissioning, the user
> can:
> # Send request to delete the node from the cluster
> # Diagnose why the node had issues with the decommission (out of memory, no
> network connection, etc) and address the issue
> # Restart NiFi on the node to so that it will reconnect to the cluster
> # Go through the steps to decommission and remove a node
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (NIFI-5585) Decommision Nodes from Cluster
[ https://issues.apache.org/jira/browse/NIFI-5585?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jeff Storck updated NIFI-5585: -- Description: Allow a node in the cluster to be decommissioned, rebalancing flowfiles on the node to be decommissioned to the other active nodes. This work depends on NIFI-5516. (was: Decommission nodes from the cluster, rebalancing flowfiles on the decommissioned nodes. This work is based off of the work done in NIFI-5516.) > Decommision Nodes from Cluster > -- > > Key: NIFI-5585 > URL: https://issues.apache.org/jira/browse/NIFI-5585 > Project: Apache NiFi > Issue Type: Improvement > Components: Core Framework >Affects Versions: 1.7.1 >Reporter: Jeff Storck >Assignee: Jeff Storck >Priority: Major > > Allow a node in the cluster to be decommissioned, rebalancing flowfiles on > the node to be decommissioned to the other active nodes. This work depends > on NIFI-5516. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
