Re: ApiVersionsResponse writes apiKeys prepended with two bytes instead of one byte.

, the client sends the subsequent metadata request and other messages. Therefore, what is the guidance w.r.t. setting the response header version? On Sat, Nov 2, 2024 at 8:44 PM Chain Head wrote: > Hi, > I am implementing broker as a hobby project. Here is the high level flow. > >

ApiVersionsResponse writes apiKeys prepended with two bytes instead of one byte.

Hi, I am implementing broker as a hobby project. Here is the high level flow. 1. Set up a response header with correlation ID and header version (1). 2. Create an `ApiVersionCollection` and add APIs. For now, I have added only two - `PRODUCE` and `METADATA` with min, max versions and no tagged fie

Re: Kafka wire protocol - Request and response versions.

Yurchenko wrote: > 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

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

github.com/a0x8o/kafka/blob/54eff6af115ee647f60129f2ce6a044cb17215d0/core/src/main/scala/kafka/api/ProducerResponse.scala#L68 > > On Sun, Oct 27, 2024, 17:42 Chain Head wrote: > > > (Apologies - I sent the same mail to the dev mailing list by mistake!) > > > > Hello, > &g

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

t > a decade since then… > > -Steve > > > On Oct 27, 2024, at 12:42 PM, Chain Head wrote: > > > > (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 me

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.

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

Re: Extracting key-value pair from Produce Request API.

ache.org/39/javadoc/org/apache/kafka/clients/consumer/ConsumerRecord.html > > Hope this helps, > Greg > > On Fri, Dec 27, 2024, 10:19 AM Chain Head wrote: > > > Hi, > > I am struggling to get the key-value pair from the Produce Request API. I > > want to write it to

Re: Extracting key-value pair from Produce Request API.

ache.org/39/javadoc/org/apache/kafka/clients/consumer/ConsumerRecord.html > > Hope this helps, > Greg > > On Fri, Dec 27, 2024, 10:19 AM Chain Head wrote: > > > Hi, > > I am struggling to get the key-value pair from the Produce Request API. I > > want to write it to

Extracting key-value pair from Produce Request API.

Hi, I am struggling to get the key-value pair from the Produce Request API. I want to write it to a Buffer for further processing. I can't seem to get the `k` and `v` values whereas the `.keySize` and `.valueSize` are reported correctly. Please advise how to extract the key value pairs from the Pro

Re: JoinGroup API response timing.

ally do both or not do both). For exactly-once > semantics, the application would need to use Kafka transactions and store > offsets in Kafka. > > -Artem > > On Wed, Jan 22, 2025 at 5:56 PM Chain Head wrote: > > > I wanted to understand the motivation for consumer group

Re: Extracting key-value pair from Produce Request API.

, 2024 at 7:01 AM David Finnie wrote: > Hi Chain Head, > > Are you seeing any errors, or just getting empty strings for k and v? > > If you are seeing empty strings, it could well be that the ByteBuffer > returned by Record.key() and Record.value() have their position set to > th

JoinGroup API response timing.

Assume that three consumers of a certain group want to connect to a broker for a topic with 3 partitions. After the FindCoordinator API is done, the consumers send JoinGroup. Since the broker cannot know in advance how many consumers are expected to join, it waits group.initial.rebalance.delay.ms b

Re: JoinGroup API response timing.

; barrier for all members. > All JoinGroup member responses are returned after all JoinGroup member > requests are received. > > Thanks, > Greg > > On Tue, Jan 21, 2025 at 7:10 AM Chain Head wrote: > > > Assume that three consumers of a certain group want to connect to a &

Re: JoinGroup API response timing.

if a consumer fails or is kicked > off the group because it times out etc then the remainder of the consumers > are rebalanced across the partitions etc. Paul > > From: Chain Head > Date: Wednesday, 22 January 2025 at 5:19 pm > To: users@kafka.apache.org > Subject: Re: J

Re: JoinGroup API response timing.

+Protocol > [3] > > https://cwiki.apache.org/confluence/display/KAFKA/KIP-932%3A+Queues+for+Kafka > > On Tue, Jan 21, 2025 at 4:41 PM Chain Head wrote: > > > Thanks. > > > > By "classic" you mean pre-KRaft consensus? What is the "current"