[
https://issues.apache.org/jira/browse/KAFKA-15686?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17781206#comment-17781206
]
Philip Nee edited comment on KAFKA-15686 at 10/31/23 4:03 AM:
--------------------------------------------------------------
[~ihavenoem...@163.com] - What is the use case of knowing which broker is down
from client's prospective? If telemetry is set up for your kafka cluster, you
should be able to tell by looking at the broker side metrics. It would be
helpful to articulate a clear case to help community to understand the
rationale behind the ask. Thanks.
was (Author: JIRAUSER283568):
[~ihavenoem...@163.com] - What is the use case of knowing which broker is down?
If telemetry is set up for your kafka cluster, you should be able to tell by
looking at the broker side metrics. It would be helpful to articulate a clear
case to help community to understand the rationale behind the ask. Thanks.
> 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)
