[
https://issues.apache.org/jira/browse/NIFI-13659?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17877724#comment-17877724
]
ASF subversion and git services commented on NIFI-13659:
--------------------------------------------------------
Commit 71face8ea788a85a53a48df2b0a872d2ea0a2f89 in nifi's branch
refs/heads/main from Bryan Bende
[ https://gitbox.apache.org/repos/asf?p=nifi.git;h=71face8ea7 ]
NIFI-13659 Call migrateProperties on components changed in synchronization
(#9201)
Signed-off-by: David Handermann <[email protected]>
> Issue migrating properties during rolling upgrade
> -------------------------------------------------
>
> Key: NIFI-13659
> URL: https://issues.apache.org/jira/browse/NIFI-13659
> Project: Apache NiFi
> Issue Type: Bug
> Affects Versions: 2.0.0-M4
> Reporter: Bryan Bende
> Assignee: Bryan Bende
> Priority: Major
> Time Spent: 20m
> Remaining Estimate: 0h
>
> The following scenario causes property migration to not work as expected:
> * Multi node cluster, 3 nodes running version X
> * A component from version Y has implemented migrateProperties, say a
> processor converts a property to a controller service for example
> * Start performing a rolling upgrade...
> * Stop node 3, upgrade libs, start node 3
> * Node 3 loads flow from disk and converts old properties to new (makes new
> CS)
> * Node 3 connects to cluster and gets the coordinator's flow which has this
> component with it's old config
> * It runs flow synchronization which undoes the migration and puts the
> config back how it was before, which now makes the processors on node 3
> invalid
> * Proceed with the remaining nodes and they will all end up in the same state
> * Only way to fully correct is for all nodes to go down at the same time so
> they can all migrate before any node joins the cluster
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
