[
https://issues.apache.org/jira/browse/NIFI-10338?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17579025#comment-17579025
]
Andreas Adamides commented on NIFI-10338:
-----------------------------------------
# *Scaling down* Nifi cluster, i.e. from 3->1 node
# Doing *changes* while on 1 node, i.e. adding a parameter context or changing
flows
# *Scaling up* Nifi Cluster, i.e. from 1-> 3 nodes
# This results in sync issues, since when step(1) occurs, only the Kubernetes
pod gets deleted, and not the Kubernetes *PVC* relating to state of parameter
contexts. Then, when (3) occurs, there are multiple *exceptions* occurring
because the PVC of the nodes that were missing , do not know about the changes.
Repeating the above, but deleting the flowfile repository PVC before (3),
solves the issue
> When adding more nodes in a Nifi Cluster mode, new nodes cannot find existing
> parameter contexts
> ------------------------------------------------------------------------------------------------
>
> Key: NIFI-10338
> URL: https://issues.apache.org/jira/browse/NIFI-10338
> Project: Apache NiFi
> Issue Type: Bug
> Components: NiFi Stateless
> Affects Versions: 1.16.1
> Environment: Kubernetes, Docker Image is based on Alpine/Java
> amazoncorreto: 8u312
> Reporter: Andreas Adamides
> Priority: Critical
>
> My setup is Nifi in Cluster mode, initially with 1 node. I have created a
> parameter context and associated it with process groups(>1) in my Canvas.
> When I increase to three nodes(they successfully connect in the cluster), and
> when I reach the Nifi UI, to view/edit that very same parameter context I get
> the error:
> {code:java}
> No parameter context with id: "<Uuid>"
> {code}
> I also get the same error when I try to reach the parameter context via the
> APIs. When I list all parameter contexts this param context shows up, but
> when I try to modify or even delete via API call, I get the same error.
> When I scale back to 1 node, repeat the above in the Nifi UI, I can view/edit
> the parameter context without any issues.
> If it matters I am using [https://github.com/cetic/helm-nifi] to deploy my
> Nifi Cluster. I suspect there might be a sync issue at some point, causing
> the new nodes to not know about that parameter context, but I cannot tell
> which one.
> Can anyone please suggest a fix or any pointers as to how to approach this
> issue?
--
This message was sent by Atlassian Jira
(v8.20.10#820010)