[
https://issues.apache.org/jira/browse/NIFI-16378?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18119442#comment-18119442
]
ASF subversion and git services commented on NIFI-16378:
--------------------------------------------------------
Commit d61be1197c4951417095486d8e0630e65379109f in nifi's branch
refs/heads/main from Mark Payne
[ https://gitbox.apache.org/repos/asf?p=nifi.git;h=d61be1197c4 ]
NIFI-16378: Handle disabled Processors during Connector drain (#11709)
Co-authored-by: Cursor <[email protected]>
> 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
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> 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)
