You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@samza.apache.org by "Hai Lu (Jira)" <ji...@apache.org> on 2019/11/07 00:06:04 UTC
[jira] [Updated] (SAMZA-2348) Notifying BEM about
kafkaConsumerProxy failure via kafkaConsumer to prevent BEM poll blocking
in case of proxy failures
[ https://issues.apache.org/jira/browse/SAMZA-2348?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Hai Lu updated SAMZA-2348:
--------------------------
Fix Version/s: 1.3
> Notifying BEM about kafkaConsumerProxy failure via kafkaConsumer to prevent BEM poll blocking in case of proxy failures
> -----------------------------------------------------------------------------------------------------------------------
>
> Key: SAMZA-2348
> URL: https://issues.apache.org/jira/browse/SAMZA-2348
> Project: Samza
> Issue Type: Bug
> Reporter: Rayman
> Priority: Major
> Fix For: 1.3
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> The problem is that a container's startup blocks indefinitely during Changelog / Checkpoint / Coordinator stream read,
> whenever the KafkaConsumerProxy fails for some reason (e.g., TopicAuth).
> This is because the SSPIterator keeps blocking on the blocking poll even when KafkaConsumerProxy stops due to exceptions thrown from KafkaConsumer.
> The fix is to allow KafkaConsumerProxy to report exceptions to KafkaSystemConsumer, which then relays it to BEM.
> BEM checks if there are any exceptions when doing a poll and re-throws.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)