[
https://issues.apache.org/jira/browse/NIFI-15475?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18053672#comment-18053672
]
ASF subversion and git services commented on NIFI-15475:
--------------------------------------------------------
Commit f81bfc393464d12e922685c7fe267b8f788fb03d in nifi's branch
refs/heads/main from Pierre Villard
[ https://gitbox.apache.org/repos/asf?p=nifi.git;h=f81bfc3934 ]
NIFI-15475 Blocked concurrent commits overwriting changes with git-based
Registry Clients (#10778)
Signed-ff-by: David Handermann <[email protected]>
> Possible concurrent flow commits are overwriting changes with git-based
> registry clients
> ----------------------------------------------------------------------------------------
>
> Key: NIFI-15475
> URL: https://issues.apache.org/jira/browse/NIFI-15475
> Project: Apache NiFi
> Issue Type: Bug
> Reporter: Geoff Greene
> Assignee: Pierre Villard
> Priority: Major
> Time Spent: 50m
> Remaining Estimate: 0h
>
> This looks like it is very related to NIFi-14478, but its still happening in
> 2.7.2:
> So, under the assumption that nifi-registry [which we rely quite heavily on]
> is going to go away, I looked at the replacement, which I gather is
> GitlabFlow Registry client (with a gitlab backing store)
> With both nifi 2.7.2 and nifi 2.6.0:
>
> # Create a simple flow, and check it into the Gitlab FlowRegistry.
> # Reimport that flow, so we now have TWO identical copies of that flow
> # Change one copy of the flow, and check it in
> # The red upgrade needed flag in the upper left corner of the OTHER flow
> doesn’t appear after many minutes. The greene checkmark remains on both,
> even though one is out of date. This is really bad for us.
> # Eventually the red upgrade flag appears SOMETIMES, but not consitsently
> # Unfortunately, and to make things worse, if you then attempt to make
> another change in the pasted OTHER flow, it doesn’t recognize the conflict,
> and that change actually overwrites the change you made in step 3.
> For what its worth, this does not appear to be the case using regular (old)
> nifi-registry.
> Restarting nifi between steps 3 and 4 does make the red upgrade flag appear,
> even in 2.7.2
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
