Gentle bump on KAFKA-16371 (Unstable committed offsets after triggering commits where metadata for some partitions are over the limit)

Hi there! Created https://issues.apache.org/jira/browse/KAFKA-16371 few weeks back but there wasn't any attention. Any chance someone knowing that code could take a look at the issue found and proposed fixed? Thanks in advance. -- BR, Michał Łowicki

Re: Gentle bump on KAFKA-16371 (Unstable committed offsets after triggering commits where metadata for some partitions are over the limit)

BR, Michał Łowicki On Fri, 5 Apr 2024 at 15:59, David Jacot wrote: > Thanks, Michal. Let me add it to my review queue. Gentle ping ;-) > > BR, > David > > On Fri, Apr 5, 2024 at 3:29 PM Michał Łowicki wrote: > > > Hi there! > > > > Created http

Metadata requests for subset of partitions

Hi there! Is there any reason why Metadata requests do not support fetching metadata for subsets of the partitions? If a certain client is interested only in e.g. 1 but topic may have many so most of fetched data isn't really used.

Re: Metadata requests for subset of partitions

On Thu, Feb 27, 2025 at 5:39 PM Kirk True wrote: > Hi Michał, > > On Thu, Feb 27, 2025, at 3:44 AM, Michał Łowicki wrote: > > Hi there! > > > > Is there any reason why Metadata requests > > <https://kafka.apache.org/protocol.html#The_Messages_Metadata> d

Re: Metadata requests for subset of partitions

f partitions at the protocol looked like a nice addition to the protocol. > > [0] - > https://github.com/apache/kafka/blob/8b605bd3620268214a85c8a520cad22dec815358/clients/src/main/resources/common/message/MetadataResponse.json#L77-L90 > > Best, > Stan > > On 2025/02/28 12

Re: Metadata requests for subset of partitions

We've an in-house client and frequently for topics with hundreds or thousands of partitions, the consumption is spread across a significant number of consumers where each one is interested in a few partitions. 1000 partitions, 200 consumers where each gets 5 partitions. Currently each one on