You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jira@kafka.apache.org by "Philip Nee (Jira)" <ji...@apache.org> on 2023/10/27 06:43:00 UTC
[jira] [Commented] (KAFKA-15686) Consumer should be able to detect network problem
[ https://issues.apache.org/jira/browse/KAFKA-15686?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17780187#comment-17780187 ]
Philip Nee commented on KAFKA-15686:
------------------------------------
Hi [~ihavenoemail@163.com] - If the leader is not presented in the current metadata, it should trigger metadata refresh. However, that shouldn't change the way you poll the consumer, because you need to continue to poll to drive the network IO and various consumer tasks.
May I ask what kind of failure scenario are you seeing? The client shouldn't even try to send a request if the leader is not present. Could you provide the error messages you see for us to understand the issue?
> Consumer should be able to detect network problem
> -------------------------------------------------
>
> Key: KAFKA-15686
> URL: https://issues.apache.org/jira/browse/KAFKA-15686
> Project: Kafka
> Issue Type: New Feature
> Components: consumer
> Affects Versions: 3.5.0
> Reporter: Jiahongchao
> Priority: Minor
>
> When we call poll method in consumer, it will return normally even if some partitions do not have a leader.
> What should we do to detect such failures? Currently we have to check log to find out broker connection problem.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)