You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@nifi.apache.org by "Vasily Gudoshnikov (Jira)" <ji...@apache.org> on 2020/11/25 07:57:00 UTC
[jira] [Comment Edited] (NIFI-8040) Failed to update Flow on all
nodes in cluster due to Cannot modify Processor configuration while the
Processor is running
[ https://issues.apache.org/jira/browse/NIFI-8040?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17238587#comment-17238587 ]
Vasily Gudoshnikov edited comment on NIFI-8040 at 11/25/20, 7:56 AM:
---------------------------------------------------------------------
[~bbende] The issue is actual at least for 1.12.1 and 1.11.4
was (Author: vgoodvin):
[~bbende] The issue is actual for 1.12.1 and 1.11.4
> Failed to update Flow on all nodes in cluster due to Cannot modify Processor configuration while the Processor is running
> -------------------------------------------------------------------------------------------------------------------------
>
> Key: NIFI-8040
> URL: https://issues.apache.org/jira/browse/NIFI-8040
> Project: Apache NiFi
> Issue Type: Bug
> Components: Core Framework
> Reporter: Vasily Gudoshnikov
> Priority: Major
> Labels: registry
> Attachments: ProcessorNode.patch, image-2020-11-24-15-57-26-995.png
>
>
> Relates to NIFI-5227
> Steps to reproduce:
> # Create a simple flow: *GenerateFlowFile + UpdateAttribute*. Ensure both processors have valid state.
> # Commit flow to a registry.
> # Remove connection between processors or do something else to move *UpdateAttribute* in invalid state.
> # Commit flow to a registry.
> # Change flow version to "1". *UpdateAttribute* should be valid now.
> # Run *UpdateAttribute*
> # Change flow version to "2". Ensure *UpdateAttribute* has invalid state now.
> # Change flow version back to "1".
> You will see error message _"Failed to update Flow on all nodes in cluster due to Cannot modify Processor configuration while the Processor is running"._
> _!image-2020-11-24-15-57-26-995.png!_
> Error message for single node (non cluster) will be similar.
> See attached patch. My solution is quite simple but I don't sure may be it is not good enough.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)