[
https://issues.apache.org/jira/browse/SAMZA-2348?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rayman updated SAMZA-2348:
--------------------------
Description:
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.
> 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
> Time Spent: 10m
> 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)
