[
https://issues.apache.org/jira/browse/KAFKA-7870?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17600910#comment-17600910
]
Chenxi Zhao commented on KAFKA-7870:
Seeing this on kafka-clients 3.2.0. An observed pattern is that
[
https://issues.apache.org/jira/browse/KAFKA-7870?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17418584#comment-17418584
]
Amar Bogari commented on KAFKA-7870:
We are running kafka 2.4.0 and see similar issues and deleted
[
https://issues.apache.org/jira/browse/KAFKA-7870?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17418435#comment-17418435
]
priya Vijay commented on KAFKA-7870:
We are running kafka 2.8 and see similar issues. We have 3
[
https://issues.apache.org/jira/browse/KAFKA-7870?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17309487#comment-17309487
]
kai.tian commented on KAFKA-7870:
-
Hi Tyran, when our borker had this exception, we found that the value
[
https://issues.apache.org/jira/browse/KAFKA-7870?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17309279#comment-17309279
]
Tyran commented on KAFKA-7870:
--
Hi Kai, we have set our open file limit to 10 and our brokers do not
[
https://issues.apache.org/jira/browse/KAFKA-7870?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17309275#comment-17309275
]
kai.tian commented on KAFKA-7870:
-
If the exception occurs in the broker section, this KAFKA-7757
[
https://issues.apache.org/jira/browse/KAFKA-7870?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17308590#comment-17308590
]
kai.tian commented on KAFKA-7870:
-
We also encountered this problem in version 2.1.0, which resulted in
[
https://issues.apache.org/jira/browse/KAFKA-7870?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17308153#comment-17308153
]
Tyran commented on KAFKA-7870:
--
Picked up a similar issue in 2.7 which causes the entire cluster to go down:
[
https://issues.apache.org/jira/browse/KAFKA-7870?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17301470#comment-17301470
]
ShiminHuang commented on KAFKA-7870:
We actually found this in version 2.4.1 as well
> Error sending
[
https://issues.apache.org/jira/browse/KAFKA-7870?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17256844#comment-17256844
]
Suo L. commented on KAFKA-7870:
---
Recently I meet and fix a bug has similar exception like this. It was
[
https://issues.apache.org/jira/browse/KAFKA-7870?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17221144#comment-17221144
]
Leonardo Vasconcellos commented on KAFKA-7870:
--
Same thing here.
2020-10-27 01:50:17.619
[
https://issues.apache.org/jira/browse/KAFKA-7870?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17220237#comment-17220237
]
Eran Levy commented on KAFKA-7870:
--
Experiencing that with 2.6.0
[
https://issues.apache.org/jira/browse/KAFKA-7870?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=1724#comment-1724
]
Gowtham commented on KAFKA-7870:
{code:java}
o.a.k.c.FetchSessionHandler pool-18-thread-1 [INFO]
[
https://issues.apache.org/jira/browse/KAFKA-7870?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17193444#comment-17193444
]
Akshesh Doshi commented on KAFKA-7870:
--
I have been observing similar logging for one of our
[
https://issues.apache.org/jira/browse/KAFKA-7870?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17158850#comment-17158850
]
VinayKumar commented on KAFKA-7870:
---
The same issue is seen in 2.4.1 version also. Can there be fix
[
https://issues.apache.org/jira/browse/KAFKA-7870?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17128301#comment-17128301
]
Luiz Ferraz commented on KAFKA-7870:
We just got a similar error on Kafka Streams
[2020-06-08
[
https://issues.apache.org/jira/browse/KAFKA-7870?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17119843#comment-17119843
]
Prashant C commented on KAFKA-7870:
---
Hit following error and after that it could not recover from
[
https://issues.apache.org/jira/browse/KAFKA-7870?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17110489#comment-17110489
]
Nicolas Martinez Varsi commented on KAFKA-7870:
---
Any news on this? We upgraded from 2.0.0
[
https://issues.apache.org/jira/browse/KAFKA-7870?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17087605#comment-17087605
]
shiva commented on KAFKA-7870:
--
yes, They are persistent.
2020-04-20 07:25:18,492 [WARN] [knode-02] -
[
https://issues.apache.org/jira/browse/KAFKA-7870?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17087603#comment-17087603
]
shiva commented on KAFKA-7870:
--
yes, They are persistent.
2020-04-20 07:25:18,492 [WARN] [knode-02] -
[
https://issues.apache.org/jira/browse/KAFKA-7870?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17087147#comment-17087147
]
Ismael Juma commented on KAFKA-7870:
Disconnections can happen for many reasons. Are the errors
[
https://issues.apache.org/jira/browse/KAFKA-7870?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17087129#comment-17087129
]
shiva commented on KAFKA-7870:
--
I wonder how do we handle these on production? I'm currently using 2.1.0
[
https://issues.apache.org/jira/browse/KAFKA-7870?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17087128#comment-17087128
]
shiva commented on KAFKA-7870:
--
I wonder how do we handle these on production? I'm currently using 2.1.0
[
https://issues.apache.org/jira/browse/KAFKA-7870?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17030903#comment-17030903
]
SVETLANA PETROVA commented on KAFKA-7870:
-
We have the same problem with kafka 2.12-2.3.0. Any
[
https://issues.apache.org/jira/browse/KAFKA-7870?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16990592#comment-16990592
]
VinayKumar commented on KAFKA-7870:
---
As mentioned by [~ayusman] in the above comment, if the same issue
[
https://issues.apache.org/jira/browse/KAFKA-7870?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16987971#comment-16987971
]
jfc commented on KAFKA-7870:
Same problem on 2.2.0-19
> Error sending fetch request (sessionId=1578860481,
[
https://issues.apache.org/jira/browse/KAFKA-7870?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16980103#comment-16980103
]
Maciej Radochonski commented on KAFKA-7870:
---
Kafka Client 2.3.1
{code:java}
Error sending fetch
[
https://issues.apache.org/jira/browse/KAFKA-7870?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16930610#comment-16930610
]
Ayusman Dikshit commented on KAFKA-7870:
Has anyone encountered this in client 2.3.0?
We are
[
https://issues.apache.org/jira/browse/KAFKA-7870?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16826664#comment-16826664
]
Liu commented on KAFKA-7870:
We actually found this in version 2.1.1 as well
> Error sending fetch request
[
https://issues.apache.org/jira/browse/KAFKA-7870?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16755870#comment-16755870
]
Maurits Hartman commented on KAFKA-7870:
Any progress on this issue? We actually experience the
[
https://issues.apache.org/jira/browse/KAFKA-7870?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16753362#comment-16753362
]
Anunya commented on KAFKA-7870:
---
Submit
> Error sending fetch request (sessionId=1578860481,
[
https://issues.apache.org/jira/browse/KAFKA-7870?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16752629#comment-16752629
]
Christoffer Hammarström commented on KAFKA-7870:
Sounds like KAFKA-7697
> Error sending
32 matches
Mail list logo