[
https://issues.apache.org/jira/browse/KAFKA-4669?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16000574#comment-16000574
]
Ismael Juma commented on KAFKA-4669:
The issue is that if we can't retrieve the channel, then we
[
https://issues.apache.org/jira/browse/KAFKA-4669?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16000562#comment-16000562
]
Mickael Maison commented on KAFKA-4669:
---
Yes that's right, if the channel was being closed, we don't
[
https://issues.apache.org/jira/browse/KAFKA-4669?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16000558#comment-16000558
]
Ismael Juma commented on KAFKA-4669:
Thanks [~mimaison], it could also be that `channel` is `null`.
>
[
https://issues.apache.org/jira/browse/KAFKA-4669?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16000552#comment-16000552
]
Mickael Maison commented on KAFKA-4669:
---
We have hit this issue again while running 0.10.2.1:
[
https://issues.apache.org/jira/browse/KAFKA-4669?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15991488#comment-15991488
]
Shannon Carey commented on KAFKA-4669:
--
We encountered this exception with our 0.9.0.1 client too,
[
https://issues.apache.org/jira/browse/KAFKA-4669?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15902986#comment-15902986
]
Paul Slater commented on KAFKA-4669:
+1 for fixing the client as well. Similar hang occurred for me
[
https://issues.apache.org/jira/browse/KAFKA-4669?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15901349#comment-15901349
]
Edoardo Comar commented on KAFKA-4669:
--
thanks [~ijuma] yes we're planning to move to 0.10.2 very
[
https://issues.apache.org/jira/browse/KAFKA-4669?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15901095#comment-15901095
]
Ismael Juma commented on KAFKA-4669:
By the way, the code where the NPE was happening changed in
[
https://issues.apache.org/jira/browse/KAFKA-4669?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15901075#comment-15901075
]
Edoardo Comar commented on KAFKA-4669:
--
The NPE moved from broker1 to another broker when the former
[
https://issues.apache.org/jira/browse/KAFKA-4669?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15899847#comment-15899847
]
Edoardo Comar commented on KAFKA-4669:
--
[~ijuma] It's the same NPE as
[
https://issues.apache.org/jira/browse/KAFKA-4669?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15899835#comment-15899835
]
Ismael Juma commented on KAFKA-4669:
It seems plausible that if that NPE happens, we process the next
[
https://issues.apache.org/jira/browse/KAFKA-4669?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15899832#comment-15899832
]
Ismael Juma commented on KAFKA-4669:
That NPE looks like KAFKA-3689.
> KafkaProducer.flush hangs when
[
https://issues.apache.org/jira/browse/KAFKA-4669?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15899827#comment-15899827
]
Edoardo Comar commented on KAFKA-4669:
--
We have found a strong correlation between the clients
[
https://issues.apache.org/jira/browse/KAFKA-4669?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15898828#comment-15898828
]
Hai Lin commented on KAFKA-4669:
For us, it only happened when the network of Kafka cluster is saturated.
[
https://issues.apache.org/jira/browse/KAFKA-4669?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15898829#comment-15898829
]
Hai Lin commented on KAFKA-4669:
For us, it only happened when the network of Kafka cluster is saturated.
[
https://issues.apache.org/jira/browse/KAFKA-4669?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15897746#comment-15897746
]
Edoardo Comar commented on KAFKA-4669:
--
We've seen this same exception using 10.0.1 clients against
[
https://issues.apache.org/jira/browse/KAFKA-4669?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15897747#comment-15897747
]
Edoardo Comar commented on KAFKA-4669:
--
It's easy to discard and recreate the consumer instance to
[
https://issues.apache.org/jira/browse/KAFKA-4669?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15893563#comment-15893563
]
Hai Lin commented on KAFKA-4669:
We have the same issue with Kafka 0.8.2.1 to Kafka 0.9 cluster. We are
[
https://issues.apache.org/jira/browse/KAFKA-4669?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15888126#comment-15888126
]
Federico Giraud commented on KAFKA-4669:
We had the same issue with a Kafka 0.8.2.0 producer and a
[
https://issues.apache.org/jira/browse/KAFKA-4669?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15834117#comment-15834117
]
Ismael Juma commented on KAFKA-4669:
The reason why there's no try/catch in `handleCompletedReceives`
[
https://issues.apache.org/jira/browse/KAFKA-4669?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15834053#comment-15834053
]
huxi commented on KAFKA-4669:
-
Maybe we could invoke an alternative method `ProduceRequestResult#await(long,
21 matches
Mail list logo
