You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@nifi.apache.org by "Bryan Bende (Jira)" <ji...@apache.org> on 2026/09/25 18:22:00 UTC

[jira] [Resolved] (NIFI-16378) Connector fails to drain if flow contains a disabled Processor

     [ https://issues.apache.org/jira/browse/NIFI-16378?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Bryan Bende resolved NIFI-16378.
--------------------------------
    Fix Version/s: 2.13.0
       Resolution: Fixed

> 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
>             Fix For: 2.13.0
>
>          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)