[
https://issues.apache.org/jira/browse/APEXMALHAR-2506?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16044838#comment-16044838
]
ASF GitHub Bot commented on APEXMALHAR-2506:
--------------------------------------------
GitHub user sandeshh opened a pull request:
https://github.com/apache/apex-malhar/pull/633
APEXMALHAR-2506 Added the monitoring to Kafka Consumer threads, if on…
…e of them dies then the Kafka operator is killed so that it can recover
from the proper state.
@PramodSSImmaneni please review.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/sandeshh/apex-malhar APEXMALHAR-2506
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/apex-malhar/pull/633.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #633
----
----
> 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
>
> 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.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
