[jira] [Commented] (KAFKA-1843) Metadata fetch/refresh in new producer should handle all node connection states gracefully

[ https://issues.apache.org/jira/browse/KAFKA-1843?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15827789#comment-15827789 ] Rajeev Jain commented on KAFKA-1843: I am still facing the issue addressed by [~omkreddy] in the

[jira] [Commented] (KAFKA-1843) Metadata fetch/refresh in new producer should handle all node connection states gracefully

[ https://issues.apache.org/jira/browse/KAFKA-1843?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15820892#comment-15820892 ] sandeep kumar singh commented on KAFKA-1843: in step 4 when you bring K1 up, should it not

[jira] [Commented] (KAFKA-1843) Metadata fetch/refresh in new producer should handle all node connection states gracefully

[ https://issues.apache.org/jira/browse/KAFKA-1843?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15185525#comment-15185525 ] venu commented on KAFKA-1843: - I am having similar problem , when partition is down, metadata is still

[jira] [Commented] (KAFKA-1843) Metadata fetch/refresh in new producer should handle all node connection states gracefully

[ https://issues.apache.org/jira/browse/KAFKA-1843?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14967773#comment-14967773 ] Eno Thereska commented on KAFKA-1843: - https://github.com/apache/kafka/pull/290 addressed [~omkreddy]

[jira] [Commented] (KAFKA-1843) Metadata fetch/refresh in new producer should handle all node connection states gracefully

[ https://issues.apache.org/jira/browse/KAFKA-1843?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14517659#comment-14517659 ] Ewen Cheslack-Postava commented on KAFKA-1843: -- A closely related and easily