[
https://issues.apache.org/jira/browse/NIFI-10205?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17682850#comment-17682850
]
naveen kumar saharan commented on NIFI-10205:
---------------------------------------------
The scenario is -
We were uipgrading the nifi for 1.12.1 to 1.16.3.
The flows were not having the back pressure setup. It was set to default. The
flow is checked in to registry.
while doing inplace upgrade, and when we saw the cluster state, it was
mismatching - contorller services were in disabled state.
also the PG were showing local changes, - Backpressure value set, local
variable added(the variable were same as before, no new variable added,) This
does not happen for all PG, 30% of our PG had this issue.
even if you do revet local changes these changes dont go away.
To resolve this and deploy the flows(upgrade), we added logic to commit local
changes in 1.16.3 and then deploy a one version loer. This checkin for us was a
dummy checkin to resolve the local changes conflict while deploying the flow
using automation .
Screenshot of the issue is already attached in the Jira ticket,
> Process Group variable added during NIFI upgrade
> -------------------------------------------------
>
> Key: NIFI-10205
> URL: https://issues.apache.org/jira/browse/NIFI-10205
> Project: Apache NiFi
> Issue Type: Bug
> Affects Versions: 1.16.3
> Environment: PROD
> Reporter: naveen kumar saharan
> Assignee: Simon Bence
> Priority: Major
> Attachments: image-2022-07-08-19-56-32-132.png,
> image-2022-07-08-20-04-35-585.png
>
>
> We are upgrading 1.12.1 to 1.16.3, after upgrade we are seeing weird behaviour
> # Random variable is getting added to PG
> # Local changes because of point 1 and also Local changes because of
> BackPressure 1Gb config adding to PG
> # Revert for local changes because of point 1,2 not happening. We have to
> deploy the flow after the commit local changes. Which is causing a dummy
> version in registry.
>
> !image-2022-07-08-19-56-32-132.png!
>
> !image-2022-07-08-20-04-35-585.png!
--
This message was sent by Atlassian Jira
(v8.20.10#820010)