[
https://issues.apache.org/jira/browse/NIFI-4436?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16316697#comment-16316697
]
ASF subversion and git services commented on NIFI-4436:
-------------------------------------------------------
Commit 0127b02617530491a1a55aa72395cee583083956 in nifi's branch
refs/heads/master from [~markap14]
[ https://git-wip-us.apache.org/repos/asf?p=nifi.git;h=0127b02 ]
NIFI-4436: Fixed bug that causes a deadlock when changing version of a PG.
Before this patch, an update would obtain a write lock and then recurse
downward through the child groups, obtaining write locks to update variable
registries. At the same time, if a Processor is obtaining a Controller Service,
it will obtain a Read Lock on the Process Group and then recurse upward through
the ancestors, obtaining Read Lock. If the timing is right, we can have a group
obtain a read lock, then try to obtain its parent's Read Lock. At the same
time, an update to the group could hold the Write Lock on the Process Group and
attempt to obtain a Write Lock on child (where the Processor lives), resulting
in a deadlock.
Signed-off-by: Matt Gilman <[email protected]>
> Allow Existing Process Group to be versioned
> --------------------------------------------
>
> Key: NIFI-4436
> URL: https://issues.apache.org/jira/browse/NIFI-4436
> Project: Apache NiFi
> Issue Type: Sub-task
> Components: Core Framework, Core UI
> Reporter: Matt Gilman
> Assignee: Matt Gilman
> Priority: Critical
> Fix For: 1.5.0
>
>
> For an existing unversioned Process Group, allow the user to version it,
> commit, stop version control, show outstanding changes, and revert
> outstanding changes. These should be initiated from the context menu and open
> a dialogs to allow the user to provide required input (name, description,
> registry, bucket, etc) where necessary.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
