You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@nifi.apache.org by "Mark Payne (Jira)" <ji...@apache.org> on 2022/01/26 15:05:00 UTC

[jira] [Updated] (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:all-tabpanel ]

Mark Payne updated NIFI-8040:
-----------------------------
    Fix Version/s: 1.16.0
         Assignee: Mark Payne
           Status: Patch Available  (was: Open)

> 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
>            Assignee: Mark Payne
>            Priority: Major
>              Labels: registry
>             Fix For: 1.16.0
>
>         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.20.1#820001)