yes, kafka supports ipv6
This is one example : https://mp.weixin.qq.com/s/7Zds_UiOSjwksmpjYeuehg
在 2021-09-15 20:23:05，"yangyang...@nnct-nsn.com" 写道：
>hi，dear
>I want to know if the kafka support ipv6？
>
>
>
>
>
>Ma Yangyang
>
>
>E-mail: yangyang...@nnct-nsn.com
Hi,
I have noticed an issue where the system running the kafka broker produces
a huge list of files marked as deleted before java shutdown.
Do I only have such a problem? So where is the cause?
Below is the number of found cases and a small fragment of this list.
[user@centrala.bzwbk@host
We are chasing a strange behavior for a while now - asking your help
because we ran out of ideas... maybe someone has a few good ideas/pointers?
Components we use:
* We are using Kafka 2.2.1 iirc cluster - 3 nodes setup
* Topics having 6 partitions
* We are working in Java and using
Hi Guozhang
Thanks for your response. I'm on KafkaStreams 2.8.1.
Since you asked, is KafkaStreams 3.0.0 compatible with a 2.4.1 broker?
But I found the issue.
TL;DR: I increased max.poll.interval.ms and decreased max.poll.records which
fixed the problem.
I noticed the StreamThread summary logs
Pr
Matthias, shouldn't version probing prevent this sort of thing from
happening? That is, shouldn't
a live downgrade always be possible? I know there were some bugs in the
downgrade path for
version probing in the past, but I'm pretty sure they should have been
fixed by 2.4.1
This seems like a bug t
Not sure from the top of my head. Maybe the logs could reveal something.
On 10/14/21 4:49 PM, Sophie Blee-Goldman wrote:
Matthias, shouldn't version probing prevent this sort of thing from
happening? That is, shouldn't
a live downgrade always be possible? I know there were some bugs in the
dow
