Re: Kafka wire protocol - Request and response versions.

Thanks. Just found this sentence in the guide - "The server will reject requests with a version it does not support, and will always respond to the client with exactly the protocol format it expects based on the version it included in its request." On Mon, Oct 28, 2024 at 10:25 AM Ivan Yurchenko

Re: Kafka wire protocol - Request and response versions.

Hi, The broker has to respond with the same API version (the response header doesn't even have the version field). Best, Ivan On Sun, Oct 27, 2024, at 20:22, Chain Head wrote: > Hello, > Suppose a client makes a API Versions request with version 3. Is it legal > for the broker to respond with

Kafka Tiered Storage Disablement Implement in ZK Mode Question

Hi kafka community, I read the KIP-950 which describe the disablement of kafka tiered storage. It said that zk mode won't be supported and

Kafka wire protocol and Wireshark capture don't seem to align.

(Apologies - I sent the same mail to the dev mailing list by mistake!) Hello, I set-up a simple Java client to publish a sample message to Kafka broker. I can see API Versions request v3 and response messages. I am able to map all the bytes as described here (https://kafka.apache.org/protocol.html

Kafka wire protocol - Request and response versions.

Hello, Suppose a client makes a API Versions request with version 3. Is it legal for the broker to respond with a version other than 3? Thanks.

Re: Kafka wire protocol and Wireshark capture don't seem to align.

I read the code again. In `ApiVersionsResponseData._write()`, there is a check of the version. If >=3, the API keys array is pre-prended by one byte that contains the length of the following array. Else, it is an INT32 that contains the length of the following array. So, the 0x3c in my case is the

Re: Kafka wire protocol and Wireshark capture don't seem to align.

There used to be a kafka dissector that I thought was shipped with Wireshark - does that decode this properly? I wasn’t certain if you were trying to decode it yourself or if the kafka dissector wasn’t working. I wrote something up here about using the dissector, but it’s been almost a decade

Re: Kafka wire protocol and Wireshark capture don't seem to align.

The correlation ID is in the response **header**. On Sun, Oct 27, 2024 at 10:36 PM Ömer Şiar Baysal wrote: > Hi, > > Could not able to find correlationID response for the Apiversions API, did > you mean Produce API? > > Maybe it is throttleTimeSize ? > > > https://github.com/a0x8o/kafka/blob/54e

Re: Kafka wire protocol and Wireshark capture don't seem to align.

Hi, Could not able to find correlationID response for the Apiversions API, did you mean Produce API? Maybe it is throttleTimeSize ? https://github.com/a0x8o/kafka/blob/54eff6af115ee647f60129f2ce6a044cb17215d0/core/src/main/scala/kafka/api/ProducerResponse.scala#L68 On Sun, Oct 27, 2024, 17:42 C