You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@nifi.apache.org by "David Handermann (Jira)" <ji...@apache.org> on 2025/11/20 17:08:00 UTC

[jira] [Updated] (NIFI-15180) Log initialization errors in ConsumeKinesis

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

David Handermann updated NIFI-15180:
------------------------------------
    Affects Version/s:     (was: 2.6.0)

> Log initialization errors in ConsumeKinesis
> -------------------------------------------
>
>                 Key: NIFI-15180
>                 URL: https://issues.apache.org/jira/browse/NIFI-15180
>             Project: Apache NiFi
>          Issue Type: Improvement
>          Components: Extensions
>            Reporter: Alaksiej Ščarbaty
>            Assignee: Alaksiej Ščarbaty
>            Priority: Major
>             Fix For: 2.7.0
>
>          Time Spent: 1h 40m
>  Remaining Estimate: 0h
>
> `ConsumeKinesis` processor launches KCL scheduler under the hood. If scheduler initialization fails for any reason, it's visible in the application logs only. The processor continues running tasks, without any flow files produced.
> Instead, the error should be propagated to the processor's code and then logged by a `ConsumeKinesis` processor's logger. 
> It seems that `WorkerStateChangeListener` in the KCL's `coordinatorConfig` is the right candidate.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)