[
https://issues.apache.org/jira/browse/NIFI-14616?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Handermann resolved NIFI-14616.
-------------------------------------
Fix Version/s: 2.5.0
Resolution: Fixed
> Improve logging around which components are stopped/restarted when updating
> flow
> --------------------------------------------------------------------------------
>
> Key: NIFI-14616
> URL: https://issues.apache.org/jira/browse/NIFI-14616
> Project: Apache NiFi
> Issue Type: Improvement
> Components: Core Framework
> Reporter: Mark Payne
> Assignee: Mark Payne
> Priority: Major
> Fix For: 2.5.0
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> When we update a flow, such as a versioned flow update or inheriting cluster
> flow, we sometimes need to stop some components. Generally, we will want to
> then restart them. However, sometimes we don't need to. But this can be
> confusing leading to logs such as:
> {code:java}
> In order to inherit proposed dataflow, will stop any components that will be
> affected by the update
> Stopping the following components: ...
> Starting the following components: AffectedComponentSet[inputPorts=[],
> outputPorts=[], remoteInputPorts=[], remoteOutputPorts=[], processors=[],
> parameterProviders=[], flowRegistryClients=[], controllerServices=[],
> reportingTasks=[], flowAnalysisRules=[], statelessProcessGroups=[]] {code}
> In this case, we stopped some components, but we never started them again. It
> is not clear why we didn't start them. Did the cluster have the components
> marked as stopped? Do they no longer exist? Etc. For any component that was
> running before the flow update, we should log the reason that we are not
> restarting it.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
