, latestOffset, kafkaEarliestOffset,readOffset);
>
> if (readOffset == 0 && readOffset < kafkaEarliestOffset) {
> log.warn("Resetting the offset to earliest available offset in kafka.");
> readOffset = kafkaEarliestOffset;
> }
>
> boolean end = false;
> lon
ea().getReqInfo().size())
|| (endTime - startTime) >= waitTime) {
log.info(
"Wait condition has been met... exiting the fetch loop. recordCount - {},
time exhausted - {} ms.",
msglist.size(), (endTime - startTime));
end = true;
//consumer.commitSync();
} else if (records.isEmpty()) {
emp
poorv Mittal
> wrote:
>
> > Hi All,
> > I would like to start vote on KIP-1109:
> >
> >
> https://cwiki.apache.org/confluence/display/KAFKA/KIP-1109%3A+Unifying+Kafka+Consumer+Topic+Metrics
> >
> > Discussion thread:
> > https://lists.apache.org/thread/fvn9r9lw55lyf971k6z4qnpnmq9tmm50
> >
> > Regards,
> > Apoorv Mittal
> >
>
Hi, Apoorv,
Thanks for the KIP. +1
Jun
On Thu, Dec 12, 2024 at 4:26 PM Apoorv Mittal
wrote:
> Hi All,
> I would like to start vote on KIP-1109:
>
> https://cwiki.apache.org/confluence/display/KAFKA/KIP-1109%3A+Unifying+Kafka+Consumer+Topic+Metrics
>
> Discussi
recated and will be removed in a future major Kafka
> version (5.0)."
>
> I agree with Chia-Ping that getting this into AK 4.0 would be great.
>
> Thanks,
> Andrew
>
> From: Apoorv Mittal
> Sent: 13 December 2024 00:28
> To:
Hi Apoorv,
Thanks for the KIP.
+1 (binding)
Andrew
From: Chia-Ping Tsai
Sent: 13 December 2024 01:30
To: dev@kafka.apache.org
Subject: Re: [VOTE] KIP-1109: Unifying Kafka Consumer Topic Metrics
+1 (binding)
Apoorv Mittal 於 2024年12月13日 週五 上午8:26寫道
l
Sent: 13 December 2024 00:28
To: dev@kafka.apache.org
Subject: Re: [DISCUSS] KIP-1109: Unifying Kafka Consumer Topic Metrics
Thanks Chia.
I have started the voting thread:
https://lists.apache.org/thread/fvn9r9lw55lyf971k6z4qnpnmq9tmm50
Regards,
Apoorv Mittal
On Thu, Dec 12, 2024 at 11:
[
https://issues.apache.org/jira/browse/KAFKA-17750?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Jacot resolved KAFKA-17750.
-
Fix Version/s: 4.0.0
Resolution: Fixed
> Extend kafka-consumer-groups command line t
+1 (binding)
Apoorv Mittal 於 2024年12月13日 週五 上午8:26寫道：
> Hi All,
> I would like to start vote on KIP-1109:
>
> https://cwiki.apache.org/confluence/display/KAFKA/KIP-1109%3A+Unifying+Kafka+Consumer+Topic+Metrics
>
> Discussion thread:
> https://li
gt; schema used in Graphite and the java consumer code just copied
> >> it.
> >> > > > Since
> >> > > > > > this is an issue very specific to Graphite, it's better not to
> >> > change
> >> >
Hi All,
I would like to start vote on KIP-1109:
https://cwiki.apache.org/confluence/display/KAFKA/KIP-1109%3A+Unifying+Kafka+Consumer+Topic+Metrics
Discussion thread:
https://lists.apache.org/thread/fvn9r9lw55lyf971k6z4qnpnmq9tmm50
Regards,
Apoorv Mittal
ts specific issue. I agree that
>> this
>> > is
>> > > > more
>> > > > > > like a bug than a new feature. We could probably just fix the
>> issue
>> > > in
>> > > > > the
>> > > > > > java consumer without a KIP.
>> > > &g
consumer without a KIP.
> > > > > >
> > > > > > Thanks,
> > > > > >
> > > > > > Jun
> > > > > >
> > > > > > On Fri, Nov 15, 2024 at 2:37 PM Apoorv Mittal <
> > > > apoorvmitta...@gmail.com>
&g
> > > emitted
> > > > > > topic names then we should not require a KIP per say but just fix
> > it
> > > as
> > > > > > part of jira itself. Please let me know your thoughts.
> > > > > >
> > > > > >
> > > > > On Fri, Nov 15, 2024 at 10:16 PM Apoorv Mittal <
> > > apoorvmitta...@gmail.com
> > > > >
> > > > > wrote:
> > > > >
> > > > > > Hi All,
> > > > > > I have added the Context section in the KIP as per the discussion
> > on
> > > > the
> > > > > > jira <https://issues.apache.org/jira/browse/KAFKA-12469>. Please
> > let
> > > > me
> > > > > > know if there is any feedback or I shall directly start the
> voting
> > > > > thread.
> > > > > >
> > > > > > Regards,
> > > > > > Apoorv Mittal
> > > > > >
> > > > > >
> > > > > > On Tue, Nov 12, 2024 at 12:49 PM Apoorv Mittal <
> > > > apoorvmitta...@gmail.com
> > > > > >
> > > > > > wrote:
> > > > > >
> > > > > >> Hi All,
> > > > > >> I would like to start a discussion on KIP-1109:
> > > > > >>
> > > > >
> > > >
> > >
> >
> https://cwiki.apache.org/confluence/display/KAFKA/KIP-1109%3A+Unifying+Kafka+Consumer+Topic+Metrics
> > > > > >>
> > > > > >> This KIP streamlines topic and topic-partition metrics for Kafka
> > > > > >> Consumer, emitting the user defined topic name (as like
> > > > kafka-producer).
> > > > > >>
> > > > > >> Regards,
> > > > > >> Apoorv Mittal
> > > > > >>
> > > > > >
> > > > >
> > > >
> > >
> >
>
Ravi Gupta created KAFKA-18143:
--
Summary: Kafka consumer keeps getting records on poll after
eviction from group
Key: KAFKA-18143
URL: https://issues.apache.org/jira/browse/KAFKA-18143
Project: Kafka
gt;>> +1 (binding)
>>>>
>>>> Jeff
>>>>
>>>> On 2024/11/25 15:46:04 "Lianet M." wrote:
>>>>> Thanks for the KIP and updates PoAn!
>>>>>
>>>>> +1 (binding)
>>>>>
>>>
[
https://issues.apache.org/jira/browse/KAFKA-18013?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Manikumar resolved KAFKA-18013.
---
Resolution: Fixed
> Add duration based offset reset option for Kafka consu
Lianet
>>>>
>>>> On Mon, Nov 25, 2024, 10:43 a.m. Andrew Schofield <
>>>> andrew_schofield_j...@outlook.com> wrote:
>>>>
>>>>> +1 (non-binding)
>>>>>
>>>>> Thanks,
>>>>> Andrew
>&g
t;> On Mon, Nov 25, 2024, 10:43 a.m. Andrew Schofield <
> >> andrew_schofield_j...@outlook.com> wrote:
> >>
> >>> +1 (non-binding)
> >>>
> >>> Thanks,
> >>> Andrew
> >>>
> >>> ___
Hi all,
Please give suggestion on this.please help ,Iam stuck with this.
Thanks
Giri
On Mon, 25 Nov 2024 at 9:22 AM, giri mungi wrote:
> Hi Ping,
>
> 1) Yes the records are already existent.
> 2) Yeah the Kafka broker also upgraded to 3.6 version.
> That’s why we are upgrading the client code
gt; > > >
> > > > wrote:
> > > >
> > > > > Hi All,
> > > > > I have added the Context section in the KIP as per the discussion
> on
> > > the
> > > > > jira <https://issues.apache.org/jira/
_schofield_j...@outlook.com> wrote:
>>
>>> +1 (non-binding)
>>>
>>> Thanks,
>>> Andrew
>>>
>>> ____
>>> From: David Jacot
>>> Sent: 25 November 2024 15:38
>>> To: dev@kafka.apache.org
>>&g
> +1 (non-binding)
> >
> > Thanks,
> > Andrew
> >
> >
> > From: David Jacot
> > Sent: 25 November 2024 15:38
> > To: dev@kafka.apache.org
> > Subject: Re: [VOTE] KIP-1099: Extend kafka-consumer-groups com
t: 25 November 2024 15:38
> To: dev@kafka.apache.org
> Subject: Re: [VOTE] KIP-1099: Extend kafka-consumer-groups command line
> tool to support new consumer group
>
> +1 (binding)
>
> In gmail, the discuss and the vote threads got merged somehow.
>
> On Wed, Nov 20, 2
+1 (non-binding)
Thanks,
Andrew
From: David Jacot
Sent: 25 November 2024 15:38
To: dev@kafka.apache.org
Subject: Re: [VOTE] KIP-1099: Extend kafka-consumer-groups command line tool to
support new consumer group
+1 (binding)
In gmail, the discuss and
ng new classes which simply remove the bit of
cruft which does not apply to share groups.
Thanks,
Andrew
From: David Jacot
Sent: 25 November 2024 15:08
To: dev@kafka.apache.org
Subject: Re: [DISCUSS] KIP-1099: Extend kafka-consumer-groups command line
https://cwiki.apache.org/confluence/display/KAFKA/KIP-1099%3A+Extend+kafka-consumer-groups+command+line+tool+to+support+new+consumer+group
> >
> > Discussion thread:
> > https://lists.apache.org/thread/lo64123wm3kjmjsx72xg67wvjx9nykk8
> >
> > Thanks,
> > PoAn
>
would prefer
> >> just MEMBER-EPOCH and ASSIGNMENT, and remove the "target" fields.
> >>
> >> Thanks,
> >> Andrew
> >>
> >>
> >> From: PoAn Yang
> >> Sent: 24 November 2024 15:08
>
iate. Personally, I would prefer
> just MEMBER-EPOCH and ASSIGNMENT, and remove the "target" fields.
>
> Thanks,
> Andrew
>
>
> From: PoAn Yang
> Sent: 24 November 2024 15:08
> To: dev@kafka.apache.org
> Subje
are not really appropriate. Personally, I would prefer
>> just MEMBER-EPOCH and ASSIGNMENT, and remove the "target" fields.
>>
>> Thanks,
>> Andrew
>>
>>
>> From: PoAn Yang
>> Sent: 24 November 2024
gt; just MEMBER-EPOCH and ASSIGNMENT, and remove the "target" fields.
>
> Thanks,
> Andrew
>
>
> From: PoAn Yang
> Sent: 24 November 2024 15:08
> To: dev@kafka.apache.org
> Subject: Re: [DISCUSS] KIP-1099: Extend kafka-c
Yang
Sent: 24 November 2024 15:08
To: dev@kafka.apache.org
Subject: Re: [DISCUSS] KIP-1099: Extend kafka-consumer-groups command line tool
to support new consumer group
Hi Chia-Ping,
Thanks for the suggestion.
The “isClassic” field in ConsumerGroupDescribeResponse is a boolean value, so
we can’
Hi Ping,
1) Yes the records are already existent.
2) Yeah the Kafka broker also upgraded to 3.6 version.
That’s why we are upgrading the client code also.
3) Do I need to compare any settings between old broker and new broker?
Please help.
Thanks
Giri
On Mon, 25 Nov 2024 at 6:45 AM, Chia-Ping
hi
1) The records you want to read are already existent, right?
2) Are all your code changes solely focused on upgrading the client code from
version 0.8 to 3.6? Or does the broker get upgraded as well?
Thanks,
Chia-Ping
> giri mungi 於 2024年11月25日 凌晨1:27 寫道：
>
> Hi Ping,
>
> My bad,commi
Hi Ping,
My bad,commitSync is not required.we can ignore that.
Iam calculating diff as below :
long stime = Calendar.getInstance().getTimeInMillis();
ConsumerRecords records =
consumer.poll(Duration.ofMillis(2000));
long etime = Calendar.getInstance().getTimeInMillis();
log.info("Poll Records C
hi Giri
1. Why do you call `commitSync`? it seems your application does not use the
consumer group as your use case is to random read, right?
2. how do you calculate "diff"?
giri mungi 於 2024年11月25日 週一 上午12:50寫道：
> Hi Ping,
>
> Please find the details below:
>
> 1) Kafka broker version is 3.6.1
Hi Ping,
Please find the details below:
1) Kafka broker version is 3.6.1
2) Logic Explanation:
Polls messages from Kafka using consumer.poll(Duration.ofMillis(2000)).
*Exit Conditions:* The loop exits when Message Limit > 1000 is reached:
Then the end flag is true and the loop will exit.
boo
hi
1) could you share the broker version to us?
2) could you explain how the sample code works? what is the "end"?
```
do {
ConsumerRecords < String, String > records =
consumer.poll(Duration.ofMillis(1500));
} while (!end)
```
thanks,
Chia-Ping
giri mungi 於 2024年1
Hi,
All of them are from same consumer in each poll.
Before poll we set offset to user input offset and try to consume next 1000
messages.
Thanks
Giridhar.
On Sun, 24 Nov 2024 at 8:40 PM, Chia-Ping Tsai wrote:
> hi
>
> > Poll Records Count :0diff :2004
> Poll Records Count :500 diff :943
hi
> Poll Records Count :0diff :2004
Poll Records Count :500 diff :943
Are them from the same consumer in each poll? Or they are based on
different "offset" and separate consumer's poll?
thanks,
Chia-Ping
giri mungi 於 2024年11月24日 週日 下午8:51寫道：
> Do i need to check any settings in the kaf
Hi Chia-Ping,
Thanks for the suggestion.
The “isClassic” field in ConsumerGroupDescribeResponse is a boolean value, so
we can’t use it as the protocol string.
I change the “PROTOCOL” column to “IS-CLASSIC” in kafka-consumer-groups.sh.
It returns “true” if a member is in a classic group or it’s
Do i need to check any settings in the kafka server level?
On Sun, Nov 24, 2024 at 6:19 PM giri mungi wrote:
> Hi I have set the below properties as below:
>
> props.put(ConsumerConfig.FETCH_MIN_BYTES_CONFIG,"175");
> props.put(ConsumerConfig.MAX_POLL_RECORDS_CONFIG, "500");
> props.put(Cons
Hi I have set the below properties as below:
props.put(ConsumerConfig.FETCH_MIN_BYTES_CONFIG,"175");
props.put(ConsumerConfig.MAX_POLL_RECORDS_CONFIG, "500");
props.put(ConsumerConfig.FETCH_MAX_WAIT_MS_CONFIG, "1500");
props.put(ConsumerConfig.MAX_PARTITION_FETCH_BYTES_CONFIG, "175");
Pol
hi Giridar
It seems your use case involves random reads, and you expect the consumer to
return 1000 records from server at once. Therefore, you could increase the wait
time (fetch.max.wait.ms) and fetch size (fetch.min.bytes) to receive a larger
response with as many records as possible.
A sui
Hi Yang,
*This is the old code which is perfectly doing fine and returning less than
3 seconds for all 1000 records.*
do {
FetchRequest req = new FetchRequestBuilder().clientId(clientName)
.addFetch(a_topic, a_partition, readOffset, fetchSize)
.build();
FetchResponse fetchResponse = consumer.fet
Hi Yang,
Can i get the records from kafka as bytes or compression form so that i
will take less time from kafka.
I can build messages from those bytes.Is that possible?
Can you please give suggestions on this.
Thanks,
Giridar
On Sun, Nov 24, 2024 at 3:50 PM giri mungi wrote:
> Hi Yang,
>
> T
Hi Yang,
Thanks for your reply.
Now what should I do to improve my performance?Because the old kafka code
was good in performance
These are the properties:
props.setProperty(ConsumerConfig.GROUP_ID_CONFIG, "");
props.setProperty(ConsumerConfig.ENABLE_AUTO_COMMIT_CONFIG,
"false");
props.setProp
Hi Giridar,
> *Code explanation:Fetching records is taking time for the first poll.*
> Poll Records Count: 500 diff: 1284
> Poll Records Count: 500 diff: 3
>
> For the first 500 records it took 1284 ms and next 500 records it took 4 ms
>
> *Why this much difference? I would like to improve the p
Hi Team,
Good day to you.
Iam Giridhar.I need your suggestions in kafka
performance improvement please.
*Scenario is: The user will give the offset as input and based on the
offset we need to give the next 1000 messages from kafka topic and next
offset.The kafka topic contains only one partition
ween classic and consumer
> >>>>> groups—it
> >>>>>> shows 'consumer' in classic groups, whereas it shows 'classic' in
> >>>>> consumer
> >>>>>> groups. Yes, it seems like a typo, but it's true.
>>> see that a member has the 'consumer' protocol when it's in a classic
>>>>> group.
>>>>>> Then, if the group is upgraded to a consumer group, calling
>>>>>> Admin#describeConsumerGroups again shows the protocol as &#
erGroupDescription, then we shouldn't modify the common
> > >>> MemberDescription structure. Instead, we could add a collection to
> > >>> ConsumerGroupDescription to trace members using the classic protocol,
> > >> which
> > >>> would allow us to enrich th
;>> Chia-Ping
> >>>
> >>> PoAn Yang 於 2024年11月22日 週五 下午3:46寫道：
> >>>
> >>>> Hi Lianet / Jeff,
> >>>>
> >>>> Thanks for the review.
> >>>>
> >>>> LM5: The kafka-share-groups.sh also use
;>> information.
>>>> Change to use “—describe —state —verbose” to show group level
>> information
>>>> in kafka-share-groups.sh.
>>>>
>>>> LM6: Update the example.
>>>>
>>>> LM7: Add a description to mention “—verbose”
t we will reformat the existing
> > > classic group's `--members --verbose` as well, specifically the
> > > "ASSIGNMENT" column to include the topic name?
> > >
> > > Thanks!
> > >
> > > On 2024/11/21 14:33:37 "Lianet M.
; > > > On Nov 22, 2024, at 7:35 AM, Jeff Kim wrote:
> > > >
> > > > Hi PoAn,
> > > >
> > > > JK2: Can we state in the KIP that we will reformat the existing
> > > > classic group's `--members --verbose` as well, specifical
gt;> Thanks for the updates PoAn!
> >>
> >> LM6. Just a nit, under the --describe --state --verbose the header is
> fine
> >> but the example is still missing the --state argument.
> >>
> >> LM7. Under the Proposed changes for kafka-share-groups.s
does group the topic partitions by topic
>>> but does not prefix the grouping with the topic name like you're proposal:
>>> "my_topic:0,1;new_topic:0,1". Should we do apply the same format for the
>>> classic group as well?
>>>>
>>>>
&
#x27;s
> confusing because it's presented as if the option already exists and we're
> only changing the output (which is the case for kafka-consumer-groups but
> not for kafka-share-groups)
>
> That's all on my side. Thanks!
>
> Lianet
>
> On Wed, Nov
it's
confusing because it's presented as if the option already exists and we're
only changing the output (which is the case for kafka-consumer-groups but
not for kafka-share-groups)
That's all on my side. Thanks!
Lianet
On Wed, Nov 20, 2024 at 11:12 PM PoAn Yang wrote:
the one we use from the consumer side to refer to the protocol in
>> use, just missing Share I notice).
>>
>> LM5. Regarding the change to the output for kafka-consumer-groups, the
>> command shown does not include the —state option, but the output shows
>> state info (s
ng the new “protocol” field added to MemberDescription. Should
> we consider reusing the existing GroupProtocol enum instead of String?
> (It’s the one we use from the consumer side to refer to the protocol in
> use, just missing Share I notice).
>
> LM5. Regarding the change to the o
notice).
LM5. Regarding the change to the output for kafka-consumer-groups, the
command shown does not include the —state option, but the output shows
state info (state, #members, epochs). I would guess that we want to modify
the output only when we describe a group with the —state —verbose option,
is
in the KIP as per the discussion on
> > the
> > > > jira <https://issues.apache.org/jira/browse/KAFKA-12469>. Please let
> > me
> > > > know if there is any feedback or I shall directly start the voting
> > > thread.
> > > >
> > &g
>>> If there is no further suggestion, I will start a vote thread today.
>>>>
>>>> Thanks,
>>>> PoAn
>>>>
>>>>> On Nov 15, 2024, at 11:50 PM, David Jacot
>>>> wrote:
>>>>>
>>>>> H
t; >>>
> >>> Hi,
> >>>
> >>> DJ2: Using "-" sounds good to me.
> >>>
> >>> DJ3: That seems reasonable to me.
> >>>
> >>> DJ4: Why not add it right now? I don't want to change the output
+1 (binding)
On 2024/11/18 14:52:22 PoAn Yang wrote:
> Hi All,
>
> I would like to start vote on KIP-1099:
> https://cwiki.apache.org/confluence/display/KAFKA/KIP-1099%3A+Extend+kafka-consumer-groups+command+line+tool+to+support+new+consumer+group
>
> Discussi
hy not add it right now? I don't want to change the output of the
>>> tool too many times.
>>>
>>> Best,
>>> David
>>>
>>> On Fri, Nov 15, 2024 at 3:23 PM PoAn Yang wrote:
>>>
>>>> Hi David / Andrew,
>>>
if there is any feedback or I shall directly start the voting
> > thread.
> > >
> > > Regards,
> > > Apoorv Mittal
> > >
> > >
> > > On Tue, Nov 12, 2024 at 12:49 PM Apoorv Mittal <
> apoorvmitta...@gmail.com
> > >
> > > w
> Best,
> > David
> >
> > On Fri, Nov 15, 2024 at 3:23 PM PoAn Yang wrote:
> >
> >> Hi David / Andrew,
> >>
> >> Thanks for review. Thanks Andrew for picking up kafka-share-groups.sh
> >> implementation.
> &
Regards,
> > Apoorv Mittal
> >
> >
> > On Tue, Nov 12, 2024 at 12:49 PM Apoorv Mittal >
> > wrote:
> >
> >> Hi All,
> >> I would like to start a discussion on KIP-1109:
> >>
> https://cwiki.apache.org/confluence/display/KAFKA/KI
Hi All,
I would like to start vote on KIP-1099:
https://cwiki.apache.org/confluence/display/KAFKA/KIP-1099%3A+Extend+kafka-consumer-groups+command+line+tool+to+support+new+consumer+group
Discussion thread:
https://lists.apache.org/thread/lo64123wm3kjmjsx72xg67wvjx9nykk8
Thanks,
PoAn
ng wrote:
>
>> Hi David / Andrew,
>>
>> Thanks for review. Thanks Andrew for picking up kafka-share-groups.sh
>> implementation.
>> I will handle kafka-consumer-groups.sh.
>>
>> DJ3: After discussing with @Chia-Ping Tsai, we think that using new format
Tue, Nov 12, 2024 at 12:49 PM Apoorv Mittal
> wrote:
>
>> Hi All,
>> I would like to start a discussion on KIP-1109:
>> https://cwiki.apache.org/confluence/display/KAFKA/KIP-1109%3A+Unifying+Kafka+Consumer+Topic+Metrics
>>
>> This KIP streamlines topic and topic-parti
Apoorv Mittal
wrote:
> Hi All,
> I would like to start a discussion on KIP-1109:
> https://cwiki.apache.org/confluence/display/KAFKA/KIP-1109%3A+Unifying+Kafka+Consumer+Topic+Metrics
>
> This KIP streamlines topic and topic-partition metrics for Kafka Consumer,
> emitting the user def
eview. Thanks Andrew for picking up kafka-share-groups.sh
> implementation.
> I will handle kafka-consumer-groups.sh.
>
> DJ3: After discussing with @Chia-Ping Tsai, we think that using new format
> is more clear.
>
> The new format will be like
> :,;:,
>
> Using colon(:)
Hi David / Andrew,
Thanks for review. Thanks Andrew for picking up kafka-share-groups.sh
implementation.
I will handle kafka-consumer-groups.sh.
DJ3: After discussing with @Chia-Ping Tsai, we think that using new format is
more clear.
The new format will be like
:,;:,
Using colon(:) to
Manikumar created KAFKA-18013:
-
Summary: Add duration based offset reset option for Kafka consumer
Key: KAFKA-18013
URL: https://issues.apache.org/jira/browse/KAFKA-18013
Project: Kafka
Issue
Hi PoAn,
DJ2: I was just going to comment that "-" would be a more appropriate missing
value, but
you got there first.
AS3: The examples for kafka-share-groups.sh include kafka-consumer-groups.sh in
the
command line.
If this is accepted in time, I'm happy to pick up the implem
update both output in
kafka-consumer-groups.sh and kafka-share-groups.sh.
DJ4: It looks like DescribeGroupsResponseData only has protocol type at group
level.
Both DescribeGroupsResponseData and ConsumerGroupDescribeResponseData don’t
have protocol at member level.
Could we use a followup to add it?
nd
> >> the progress of rebalancing in quite some detail. The information is
> >> really not understandable
> >> for most users who do not have deep knowledge of KIP-848/932.
> >>
> >> As a result, I suggest for kafka-share-groups.sh that you add a
&
Hi All,
I would like to start a discussion on KIP-1109:
https://cwiki.apache.org/confluence/display/KAFKA/KIP-1109%3A+Unifying+Kafka+Consumer+Topic+Metrics
This KIP streamlines topic and topic-partition metrics for Kafka Consumer,
emitting the user defined topic name (as like kafka-producer
Pratheesh M created KAFKA-17971:
---
Summary: Kafka consumer performance has been reduced drastically
when added RTT of 50ms to Kafka cluster
Key: KAFKA-17971
URL: https://issues.apache.org/jira/browse/KAFKA-17971
at you add a --members
>> --verbose option
>> and only include the new information in the output for that option, rather
>> than changing the
>> non-verbose --members output.
>>
>> I also make a similar suggestion for kafka-consumer-groups.sh --members
>> and
the
> non-verbose --members output.
>
> I also make a similar suggestion for kafka-consumer-groups.sh --members
> and only add the
> new information for the --verbose output.
>
> AS2: I strongly suggest that you use MEMBER-EPOCH instead of
> CONSUMER-EPOCH.
> I think it
/932.
As a result, I suggest for kafka-share-groups.sh that you add a --members
--verbose option
and only include the new information in the output for that option, rather than
changing the
non-verbose --members output.
I also make a similar suggestion for kafka-consumer-groups.sh --members and
[
https://issues.apache.org/jira/browse/KAFKA-16248?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alieh Saeedi resolved KAFKA-16248.
--
Resolution: Fixed
> Kafka consumer should cache leader offset ran
Hi Frank,
Thanks for the KIP!
Since we’re updating kafka-consumer-groups to add epoch information from the
new protocol, I wonder if it’s feasible to also add leader epoch information
when printing --offsets. leaderEpoch was added in KIP-320 and we neglected to
update kafka-consumer-groups at
would like to kick off the discussion of KIP-1099. This KIP enhances the
> > kafka-consumer-groups tools to include state which is introduced by KIP-848.
> >
> > KIP-1099: Extend kafka-consumer-groups command line tool to support new
> > consumer group - Apache Kafka - Apache
CONSUMER-EPOCH, not MEMBER-EPOCH? That would seem more
consistent.
Cheers,
Lucas
On Wed, Oct 23, 2024 at 2:41 PM Frank Yang wrote:
> Hi all,
>
> I would like to kick off the discussion of KIP-1099. This KIP enhances the
> kafka-consumer-groups tools to include state which is introduce
Hi all,
I would like to kick off the discussion of KIP-1099. This KIP enhances the
kafka-consumer-groups tools to include state which is introduced by KIP-848.
https://cwiki.apache.org/confluence/display/KAFKA/KIP-1099%3A+Extend+kafka-consumer-groups+command+line+tool+to+support+new+consumer
[
https://issues.apache.org/jira/browse/KAFKA-17731?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Lianet Magrans resolved KAFKA-17731.
Resolution: Fixed
> Kafka consumer client sometimes elapses wait time for terminat
David Jacot created KAFKA-17750:
---
Summary: Extend kafka-consumer-groups command line tool to support
new consumer group
Key: KAFKA-17750
URL: https://issues.apache.org/jira/browse/KAFKA-17750
Project
Apoorv Mittal created KAFKA-17731:
-
Summary: Kafka consumer client sometimes elapses wait time for
terminating telemetry push
Key: KAFKA-17731
URL: https://issues.apache.org/jira/browse/KAFKA-17731
Andrew Schofield created KAFKA-17550:
Summary: Add INCONSISTENT_GROUP_TYPE to ConsumerGroupDescribe and
kafka-consumer-groups.sh
Key: KAFKA-17550
URL: https://issues.apache.org/jira/browse/KAFKA-17550
[
https://issues.apache.org/jira/browse/KAFKA-17230?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jun Rao resolved KAFKA-17230.
-
Fix Version/s: 3.9.0
Resolution: Fixed
merged the PR to trunk
> Kafka consumer client does
Apoorv Mittal created KAFKA-17230:
-
Summary: Kafka consumer client doesn't report node request-latency
metrics
Key: KAFKA-17230
URL: https://issues.apache.org/jira/browse/KAFKA-17230
Project:
Omnia Ibrahim created KAFKA-17218:
-
Summary: kafka-consumer-groups fails to describe all group if one
group has been consuming from a deleted topic
Key: KAFKA-17218
URL: https://issues.apache.org/jira/browse
Bumping up this thread since I can not find it in the mail archive.
On Wed, 22 May 2024 at 18:09, Harsh Panchal
wrote:
> Hi,
>
> I would like to propose a change in the kafka-consumer-perf-test tool to
> support perf testing specific partitions.
>
> kafka-consumer-perf-test
1 - 100 of 645 matches
Mail list logo
