[
https://issues.apache.org/jira/browse/KAFKA-4939?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
radha updated KAFKA-4939:
-
Description:
If you have many brokers in your bootstrap.servers list and some cannot be
reached by a specific
[
https://issues.apache.org/jira/browse/KAFKA-4939?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
radha updated KAFKA-4939:
-
Description:
If you have many brokers in your bootstrap.servers list and some cannot be
reached by a specific
[
https://issues.apache.org/jira/browse/KAFKA-4939?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
radha updated KAFKA-4939:
-
Description:
If you have many brokers and some cannot be reached by a specific Kafka client
for whatever reason,
radha created KAFKA-4939:
Summary: Kafka does not log NoRouteToHostException in ERROR log
level
Key: KAFKA-4939
URL: https://issues.apache.org/jira/browse/KAFKA-4939
Project: Kafka
Issue Type: Bug
[
https://issues.apache.org/jira/browse/KAFKA-789?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15334523#comment-15334523
]
radha commented on KAFKA-789:
-
This says resolved but does not mention anything about how this works?
>
[
https://issues.apache.org/jira/browse/KAFKA-3686?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15328781#comment-15328781
]
radha commented on KAFKA-3686:
--
We have a similar issue and even with a very very large retry, the producer
