[
https://issues.apache.org/jira/browse/NIFI-16378?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mark Payne updated NIFI-16378:
------------------------------
Description:
If a Connector has a disabled processor, the drain never completes. This
appears to be a bug in the Processor Lifecycle code:
{code:java}
public CompletableFuture<Void> stop() {
return processScheduler.stopProcessor(processorNode,
ProcessorStopLifecycleMethods.TRIGGER_ALL);
}{code}
This differs from the ProcessGroup Lifecycle code, which already skips any
Processor that is stopped or disabled. We should similarly return a Completed
future from this method if the Processor is already stopped or disabled
was:
If a Connector has a disabled processor, the drain never completes. This
appears to be a bug in the Processor Lifecycle code:
{code:java}
public CompletableFuture<Void> stop() {
return processScheduler.stopProcessor(processorNode,
ProcessorStopLifecycleMethods.TRIGGER_ALL);
}{code}
This differs from the ProcessGroup Lifecycle code, which already skips any
Processor that is stopped or disabled.
> Connector fails to drain if flow contains a disabled Processor
> --------------------------------------------------------------
>
> Key: NIFI-16378
> URL: https://issues.apache.org/jira/browse/NIFI-16378
> Project: Apache NiFi
> Issue Type: Bug
> Components: Core Framework
> Reporter: Mark Payne
> Assignee: Mark Payne
> Priority: Major
>
> If a Connector has a disabled processor, the drain never completes. This
> appears to be a bug in the Processor Lifecycle code:
> {code:java}
> public CompletableFuture<Void> stop() {
> return processScheduler.stopProcessor(processorNode,
> ProcessorStopLifecycleMethods.TRIGGER_ALL);
> }{code}
> This differs from the ProcessGroup Lifecycle code, which already skips any
> Processor that is stopped or disabled. We should similarly return a Completed
> future from this method if the Processor is already stopped or disabled
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
