[
https://issues.apache.org/jira/browse/NIFI-10515?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17605988#comment-17605988
]
ASF subversion and git services commented on NIFI-10515:
--------------------------------------------------------
Commit eaa275a5e404d10358adf495802dc2bf829289b5 in nifi's branch
refs/heads/main from Mark Payne
[ https://gitbox.apache.org/repos/asf?p=nifi.git;h=eaa275a5e4 ]
NIFI-10515: If propopsed controller service is disabled, ensure that we don't
re-enable the service and references when synchronize(ControllerServiceNode...)
is called
Signed-off-by: Joe Gresock <[email protected]>
This closes #6425.
> StandardVersionedComponentSynchronizer restarting controller service when
> proposal is to be disabled
> ----------------------------------------------------------------------------------------------------
>
> Key: NIFI-10515
> URL: https://issues.apache.org/jira/browse/NIFI-10515
> Project: Apache NiFi
> Issue Type: Bug
> Components: Core Framework
> Reporter: Mark Payne
> Assignee: Mark Payne
> Priority: Minor
> Time Spent: 10m
> Remaining Estimate: 0h
>
> In the StandardVersionedComponentSynchronizer, when {{synchronize}} is called
> with a Controller Service, and the proposed VersionedControllerService has a
> ScheduledState of DISABLED, the service is disabled, along with all of its
> dependencies.
> However, if the service has any other controller services referencing it,
> they all end up being restarted, along with the service itself.
> This does not affect any services that are updated via the UI, REST API, or
> when syncing with cluster. This affects only calls going through
> StandardVersionedComponentSynchronizer.synchronize(ControllerService, ...)
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
