[
https://issues.apache.org/jira/browse/APEXMALHAR-2506?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Thomas Weise resolved APEXMALHAR-2506.
--------------------------------------
Resolution: Fixed
Fix Version/s: 3.8.0
> Kafka Input operator - needs better handling of failure of Kafka reader thread
> ------------------------------------------------------------------------------
>
> Key: APEXMALHAR-2506
> URL: https://issues.apache.org/jira/browse/APEXMALHAR-2506
> Project: Apache Apex Malhar
> Issue Type: Improvement
> Reporter: Sandesh
> Assignee: Sandesh
> Fix For: 3.8.0
>
>
> Kafka input operator has a separate thread to read from Kafka. Even if the
> Kafka reader thread is not running, the operator will continue to run.
> Ideally, following things needs to be done
> 1. More logging as to why the Kafka reader thread exited
> 2. If the Kafka reader thread gets killed either kill the container or retry
> with a new thread.
> Note: We have seen an intermittent issue, where Kafka Consumer thread has
> exited, but operator continues to be reported as in good health because the
> exception is not thrown in the operator thread. After making this change, I
> have seen this issue only once and also Kafka logged the message along the
> lines (*fetch failed*)
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
