[
https://issues.apache.org/jira/browse/NIFI-5340?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16540088#comment-16540088
]
yahor tsaryk commented on NIFI-5340:
------------------------------------
[~pvillard] Thanks for your answer. We use a lot of custom processors in NiFi
flow, I'll double check if there are any processors which wait too long for
underlying resources to be disposed. Possibly this issue also can be related to
network communication between nodes in cluster, we use Kubernetes (k8s) as our
orchestration system, so I'll check if there are any issues with nodes network.
I think this ticket can be closed as you confirmed that the Registry should
work in cluster mode without any additional settings. I'll open new issue if i
find something specific related to the above
> 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
> 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
(v7.6.3#76005)
