You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@nifi.apache.org by "Mateusz Pierzchala (Jira)" <ji...@apache.org> on 2020/08/10 12:09:00 UTC
[jira] [Commented] (NIFI-5340) Not able to update the flow using
NiFi registry when NiFi server is set as cluster mode
[ https://issues.apache.org/jira/browse/NIFI-5340?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17174272#comment-17174272 ]
Mateusz Pierzchala commented on NIFI-5340:
------------------------------------------
Hi we have the same issue when modifying parameter context- even when freshly created parameter context is not assigned to any process group:
!image-2020-08-10-14-07-32-653.png!
We haven't introduced any changes recently- it just started to happen.
> Not able to update the flow using NiFi registry when NiFi server is set as cluster mode
> ---------------------------------------------------------------------------------------
>
> Key: NIFI-5340
> URL: https://issues.apache.org/jira/browse/NIFI-5340
> Project: Apache NiFi
> Issue Type: Bug
> Reporter: yahor tsaryk
> Priority: Major
> Labels: Bug, Question, SDLC
> Attachments: NiFi Flow Version Update via Registry (failure).png
>
>
> Hello, we recently updated our NiFi version to 1.6.0 and got ability to synchronize flows in our environments via versioning i.e NiFi Registry. It works pretty well when we try to fetch the latest flow version from the Registry into a standalone NiFi server (without clustering mode).
> However, when we try to update the flow in our environments where we run NiFi in cluster mode composed of 3 nodes we got a failure:
> ```Failed to update flow to new version due to org.apache.nifi.web.util.LifecycleManagementException: Failed while waiting for components to transition to state of STOPPED```
> I attached a screenshot with this alert. Could you shed some light on this ? Does cluster mode require any additional settings in order to work with NiFi registry ? Let me know if you need more info
--
This message was sent by Atlassian Jira
(v8.3.4#803005)