[
https://issues.apache.org/jira/browse/NIFI-5619?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jeff Storck updated NIFI-5619:
------------------------------
Description:
When the cluster state for a processor is stopped, it is possible for a node to
join the cluster with that particular processor running. The UI will show the
processor as stopped, but going to the cluster summary and viewing the
node-specific status of that processor will show it's running on the node that
joined.
To reproduce this:
# Build the Node Decommissioning [PR
3010|https://github.com/apache/nifi/pull/3010]
# Create a two-node cluster, does not need to be secure
# Create a flow with a GenerateFlowFile processor connected to an
UpdateAttribute processor
# Start the GenerateFlowFile processor to let flowfiles queue in the connection
to UpdateAttribute
# Using node 1's UI, disconnect node 2 from the cluster
# Using node 1's UI, offload node 2
# Using node 1's UI, delete node 2 from the cluster
# Using node 1's UI, stop GenerateFlowFile
# Restart node 2
# Once node 2 is reconnected, in the UI the GenerateFlowFile processor will
look like it is stopped
# Go to the Cluster Summary UI and click on the View Processor Details icon
which will show the processor running on node 2
was:
When the cluster state for a processor is stopped, it is possible for a node to
join the cluster with that particular processor running. The UI will show the
processor as stopped, but going to the cluster summary and viewing the
node-specific status of that processor will show it's running on the node that
joined.
To reproduce this:
# Build the Node Decommissioning [PR
3010|https://github.com/apache/nifi/pull/3010]
# Create a two-node cluster, does not need to be secure
# Create a flow with a GenerateFlowFile processor connected to an
UpdateAttribute processor
# Start the GenerateFlowFile processor to let flowfiles queue in the connection
to UpdateAttribute
# Using node 1's UI, disconnect node 2 from the cluster
# Using node 1's UI, offload node 2
# Using node 1's UI, delete node 2 from the cluster
# Restart node 2
# Once node 2 is reconnected, in the UI the GenerateFlowFile processor will
look like it is stopped
# Go to the Cluster Summary UI and click on the View Processor Details icon
which will show the processor running on node 2
> Node can join the cluster with a processor running when cluster state for
> that processor is stopped
> ---------------------------------------------------------------------------------------------------
>
> Key: NIFI-5619
> URL: https://issues.apache.org/jira/browse/NIFI-5619
> Project: Apache NiFi
> Issue Type: Bug
> Affects Versions: 1.8.0
> Reporter: Jeff Storck
> Priority: Major
> Attachments: Screen Shot 2018-09-20 at 4.53.44 PM.png, Screen Shot
> 2018-09-20 at 4.54.07 PM.png, Screen Shot 2018-09-20 at 4.54.15 PM.png
>
>
> When the cluster state for a processor is stopped, it is possible for a node
> to join the cluster with that particular processor running. The UI will show
> the processor as stopped, but going to the cluster summary and viewing the
> node-specific status of that processor will show it's running on the node
> that joined.
> To reproduce this:
> # Build the Node Decommissioning [PR
> 3010|https://github.com/apache/nifi/pull/3010]
> # Create a two-node cluster, does not need to be secure
> # Create a flow with a GenerateFlowFile processor connected to an
> UpdateAttribute processor
> # Start the GenerateFlowFile processor to let flowfiles queue in the
> connection to UpdateAttribute
> # Using node 1's UI, disconnect node 2 from the cluster
> # Using node 1's UI, offload node 2
> # Using node 1's UI, delete node 2 from the cluster
> # Using node 1's UI, stop GenerateFlowFile
> # Restart node 2
> # Once node 2 is reconnected, in the UI the GenerateFlowFile processor will
> look like it is stopped
> # Go to the Cluster Summary UI and click on the View Processor Details icon
> which will show the processor running on node 2
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
