[
https://issues.apache.org/jira/browse/NIFI-15180?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18039666#comment-18039666
]
ASF subversion and git services commented on NIFI-15180:
--------------------------------------------------------
Commit 28589e4964d8b5f2b6a21797de0b4523a87250a0 in nifi's branch
refs/heads/main from Alaksiej Ščarbaty
[ https://gitbox.apache.org/repos/asf?p=nifi.git;h=28589e4964 ]
NIFI-15180 Log initialization errors in ConsumeKinesis (#10526)
Signed-off-by: David Handermann <[email protected]>
> 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)
