tor triggers assignment recalculation on consumer group
> upgrade due to static member replacement
> --
>
> Key: KAFKA-18687
> URL: https:/
[
https://issues.apache.org/jira/browse/KAFKA-18655?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jeff Kim resolved KAFKA-18655.
--
Resolution: Fixed
> Implement the consumer group size counter with scheduled t
Sean Quah created KAFKA-18687:
-
Summary: New group coordinator triggers assignment recalculation
on consumer group upgrade due to static member replacement
Key: KAFKA-18687
URL: https://issues.apache.org/jira/browse
Dongnuo Lyu created KAFKA-18655:
---
Summary: Implement the consumer group size counter with scheduled
task
Key: KAFKA-18655
URL: https://issues.apache.org/jira/browse/KAFKA-18655
Project: Kafka
[
https://issues.apache.org/jira/browse/KAFKA-18150?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Jacot resolved KAFKA-18150.
-
Fix Version/s: 4.0.0
Resolution: Fixed
> Maybe downgrade the consumer group i
> PlaintextAdminIntegrationTest.testConsumerGroups fails with CONSUMER group
> protocol
> ---
>
> Key: KAFKA-17960
> URL: https://issues.apache.org/jira/browse/KAFKA-17960
> Project: K
Harshit Pedamkar created KAFKA-18233:
Summary: Mirrormaker 2 All Worker tasks graceful shutdown fails
after which the consumer group offsets are replicated .
Key: KAFKA-18233
URL: https://issues.apache.org
ool to support new consumer group
>
>
> Key: KAFKA-17750
> URL: https://issues.apache.org/jira/browse/KAFKA-17750
> Project: Kafka
> Is
[
https://issues.apache.org/jira/browse/KAFKA-18221?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Lianet Magrans resolved KAFKA-18221.
Resolution: Fixed
> Set explicit consumer group protocol in streams te
Lianet Magrans created KAFKA-18221:
--
Summary: Set explicit consumer group protocol in streams tests
Key: KAFKA-18221
URL: https://issues.apache.org/jira/browse/KAFKA-18221
Project: Kafka
[
https://issues.apache.org/jira/browse/KAFKA-15284?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kirk True resolved KAFKA-15284.
---
Resolution: Won't Fix
> Implement GroupProtocolResolver to dynamically determine consum
oup fails for static consumer group member
>
>
> Key: KAFKA-18116
> URL: https://issues.apache.org/jira/browse/KAFKA-18116
> Project: Kafka
> Issue Type: Sub-task
>
Dongnuo Lyu created KAFKA-18150:
---
Summary: Maybe downgrade the consumer group if a consumer member
leaves the group though admin client
Key: KAFKA-18150
URL: https://issues.apache.org/jira/browse/KAFKA-18150
pty member id
> when using CONSUMER group
> -
>
> Key: KAFKA-18060
> URL: https://issues.apache.org/jira/browse/KAFKA-18060
> Project: Kafka
;>> Lianet
>>>>>
>>>>> On Mon, Nov 25, 2024, 10:43 a.m. Andrew Schofield <
>>>>> andrew_schofield_j...@outlook.com> wrote:
>>>>>
>>>>>> +1 (non-binding)
>>>>>>
>>>>>> Thanks,
Lianet Magrans created KAFKA-18116:
--
Summary: Admin LeaveGroup fails for static consumer group member
Key: KAFKA-18116
URL: https://issues.apache.org/jira/browse/KAFKA-18116
Project: Kafka
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
> >>>
> >>> ___
ync
> response for classic members in consumer group
>
>
> Key: KAFKA-18099
> URL: https://issues.apache.org/jira/
Dongnuo Lyu created KAFKA-18099:
---
Summary: The lkc prefix should be removed from the topic name when
generating sync response for classic members in consumer group
Key: KAFKA-18099
URL: https://issues.apache.org
_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
tool
to support new consumer group
Hi PoAn,
Thanks for the update.
Regarding the CLI, I wonder whether we should rather have a column called
"Upgraded" which is only displayed when some members use the classic
protocol. The displayed value would be True for consumer members and False
for
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
>
ct: 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’t use it as the protocol stri
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’
a classic member in
a consumer group.
In other cases, it returns “false”.
I have a draft implementation in https://github.com/apache/kafka/pull/17872.
Thanks,
PoAn
> On Nov 23, 2024, at 1:05 PM, Chia-Ping Tsai wrote:
>
> hi PoAn
>
> `isClassic` is good to me :)
>
&
n ShareGroupDescription, it’s always “false”.
>
> Thanks,
> PoAn
>
> > On Nov 23, 2024, at 1:02 AM, Chia-Ping Tsai wrote:
> >
> > hi DJ
> >
> >> My goal was to have a way to tell the user that his (new) consumer group
> > may have non-upgraded members
was to have a way to tell the user that his (new) consumer group
> may have non-upgraded members yet. I wonder if we could use a boolean to
> signal this, e.g. isLegacy. Then, in the CLI we could have a column which
> is only displayed when they are non upgraded members. What do you thin
hi DJ
> My goal was to have a way to tell the user that his (new) consumer group
may have non-upgraded members yet. I wonder if we could use a boolean to
signal this, e.g. isLegacy. Then, in the CLI we could have a column which
is only displayed when they are non upgraded members. What do
s the latter is
the name of the protocol/api used. This is indeed confusing.
My goal was to have a way to tell the user that his (new) consumer group
may have non-upgraded members yet. I wonder if we could use a boolean to
signal this, e.g. isLegacy. Then, in the CLI we could have a column which
is
Hi Chia-Ping / David,
Thanks for the review and suggestions.
>> I don't fully follow your comment so please excuse me if I say something
>> wrong.
I think Chia-Ping wants to say: originally, the default protocol in classic
group is “consumer”.
After we have a new consumer gr
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 'classic' for the
same member.
I don't fully follow your comment so please excuse me if
beConsumerGroups and
> 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 'classic' for the
> same member.
>
> I
KAFKA-12690 and the root cause is traced by KAFKA-18060
> TransactionsTest.testSendOffsetsWithGroupId fails with CONSUMER group protocol
> --
>
> Key: KAFKA-17964
> URL: https
KAFKA-12690 and the root cause is traced by KAFKA-18060
> TransactionsBounceTest.testWithGroupId fails with CONSUMER group protocol
> -
>
> Key: KAFKA-17961
> URL: https://is
/ “consumer” /
> >>> “share”.
> >>> I agree it’s better to use a type like GroupProtocol enum, but I would
> >>> like to align the format with kafka-groups.sh.
> >>> How about we use another Jira to add “SHARE” to GroupProtocol and
> change
> >&
ange
>>> return type of ModernGroup#protocolType?
>>>
>>> LM5 / JK1: Sorry, I misunderstood LM3, so I deleted —state in the title.
>>> You’re correct. I would like to use `—describe —state —verbose` to show
>>> group level information.
>>>
ype?
> >
> > LM5 / JK1: Sorry, I misunderstood LM3, so I deleted —state in the title.
> > You’re correct. I would like to use `—describe —state —verbose` to show
> > group level information.
> > For `—describe —verbose`, it will show output as same as `—desc
use `—describe —state —verbose` to show
> group level information.
> For `—describe —verbose`, it will show output as same as `—describe
> —offsets —verbose`,
> because `—describe` also shows output as same as `—describe —offsets`.
>
> JK2: Yes, I only use consumer group in the sample
Chia-Ping Tsai created KAFKA-18060:
--
Summary: new coordinator does not support v0-v2
TxnOffsetCommitRequest when using CONSUMER group
Key: KAFKA-18060
URL: https://issues.apache.org/jira/browse/KAFKA-18060
scribe —verbose`, it will show output as same as `—describe —offsets
—verbose`,
because `—describe` also shows output as same as `—describe —offsets`.
JK2: Yes, I only use consumer group in the sample output, but the classic group
will use the same format as well.
Thanks,
PoAn
> On Nov 21, 2024, a
> Thanks!
>
> Lianet
>
>
> On Wed, Nov 20, 2024 at 2:12 AM PoAn Yang wrote:
>
> > Hi Chia-Ping,
> >
> > Thanks for the review and suggestions.
> >
> > CI0: Thanks for the reminder. Update validVersions in
> > ConsumerGroupDescribeReq
otocol` to check whether
> a member in consumer group uses “classic” or “consumer” protocol.
>
> CI2: Yes, a member in share group always uses “share” protocol.
>
> CI3: Add a table to show meaning of “classic”, “consumer”, and “share”
> protocol.
>
> BTW, the vot
Hi Chia-Ping,
Thanks for the review and suggestions.
CI0: Thanks for the reminder. Update validVersions in
ConsumerGroupDescribeRequest to 0-1.
CI1: Yes, I use `ConsumerGroupMember#useClassicProtocol` to check whether a
member in consumer group uses “classic” or “consumer” protocol.
CI2: Yes
e thread next
> >> Monday.
> >>>>
> >>>> Thanks,
> >>>> PoAn
> >>>>
> >>>>> On Nov 14, 2024, at 9:05 PM, Andrew Schofield <
> >>>> andrew_schofield_j...@outlook.com> wrote:
> >>&
+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
Kirk True created KAFKA-18040:
-
Summary:
PlaintextProducerSendTest.testSendToPartitionWithFollowerShutdownShouldNotTimeout
fails with CONSUMER group protocol
Key: KAFKA-18040
URL: https://issues.apache.org/jira
t;>> PoAn
>>>>
>>>>> On Nov 14, 2024, at 9:05 PM, Andrew Schofield <
>>>> andrew_schofield_j...@outlook.com> wrote:
>>>>>
>>>>> Hi PoAn,
>>>>> DJ2: I was just going to comment that "-" wou
>>> 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
> >>&
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
a-consumer-groups.sh in the
>>> command line.
>>>
>>> If this is accepted in time, I'm happy to pick up the implementation of
>> the share groups
>>> part of this if it helps.
>>>
>>> Thanks,
>>> Andrew
>>>
>>&g
helps.
> >
> > Thanks,
> > Andrew
> >
> > ____
> > From: Frank Yang
> > Sent: 14 November 2024 10:48
> > To: dev@kafka.apache.org
> > Subject: Re: [DISCUSS] KIP-1099: Extend kafka-consumer-groups command
>
10:48
> To: dev@kafka.apache.org
> Subject: Re: [DISCUSS] KIP-1099: Extend kafka-consumer-groups command line
> tool to support new consumer group
>
> Hi David,
>
> Thanks for the review and suggestion! I would like to get this in AK 4.0 as
> well. I will do my best.
>
entation of the
share groups
part of this if it helps.
Thanks,
Andrew
From: Frank Yang
Sent: 14 November 2024 10:48
To: dev@kafka.apache.org
Subject: Re: [DISCUSS] KIP-1099: Extend kafka-consumer-groups command line tool
to support new consumer group
Hi
fka/blob/18199028a672fd973ac37bf26316994babc2a6da/tools/src/main/java/org/apache/kafka/tools/consumer/group/ConsumerGroupCommand.java#L92>)
DJ3: Update KIP to use CURRENT-EPOCH CURRENT-ASSIGNMENT TARGET-EPOCH
TARGET-ASSIGNMENT.
Remove GROUP-EPOCH.
For assignment value, it follows current
`
members and `consumer` members in a `consumer` group during an online
upgrade from the classic protocol to the consumer protocol. Having this
information may be handy for administrators. What do you think?
DJ5: In the output of `--describe --offsets --verbose`, I would suggest
putting `LEADER-EPOCH
k connector" with CONSUMER group protocol
> -
>
> Key: KAFKA-17962
> URL: https://issues.apache.org/jira/browse/KAFKA-17962
messages after
> resuming sink connector" with CONSUMER group protocol
> -
>
> Key: KAFKA-17962
> URL: https://issues.apache
Kirk True created KAFKA-17964:
-
Summary: TransactionsTest.testSendOffsetsWithGroupId fails with
CONSUMER group protocol
Key: KAFKA-17964
URL: https://issues.apache.org/jira/browse/KAFKA-17964
Project
Kirk True created KAFKA-17962:
-
Summary: test_pause_and_resume_sink fails with "Failed to consume
messages after resuming sink connector" with CONSUMER group protocol
Key: KAFKA-17962
URL: https://issues.
Kirk True created KAFKA-17961:
-
Summary: TransactionsBounceTest.testWithGroupId fails with
CONSUMER group protocol
Key: KAFKA-17961
URL: https://issues.apache.org/jira/browse/KAFKA-17961
Project: Kafka
[
https://issues.apache.org/jira/browse/KAFKA-15321?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Lianet Magrans resolved KAFKA-15321.
Resolution: Fixed
> Document consumer group member state mach
eady have "member" in the admin client such as MemberDescription.
>> It's not a
>> new term.
>>
>>
>> Thanks,
>> Andrew
>>
>> From: PoAn Yang
>> Sent: 25 October 2024 13:55
>> To: dev@
An Yang
> Sent: 25 October 2024 13:55
> To: dev@kafka.apache.org
> Subject: Re: [DISCUSS] KIP-1099: Extend kafka-consumer-groups command line
> tool to support new consumer group
>
> Hi Lucas,
>
> Thanks for the review!
>
> 1) Yes, I add related change for kafka-sha
Andrew Schofield created KAFKA-17908:
Summary: Tidy up log messages for consumer group in group metadata
manager
Key: KAFKA-17908
URL: https://issues.apache.org/jira/browse/KAFKA-17908
Project
scription. It's
not a
new term.
Thanks,
Andrew
From: PoAn Yang
Sent: 25 October 2024 13:55
To: dev@kafka.apache.org
Subject: Re: [DISCUSS] KIP-1099: Extend kafka-consumer-groups command line tool
to support new consumer group
Hi Lucas,
Thanks for th
s 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+group
> Thank you,
> PoAn
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
d by KIP-848.
>
> KIP-1099: Extend kafka-consumer-groups command line tool to support new
> consumer group - Apache Kafka - Apache Software Foundation
> <https://cwiki.apache.org/confluence/display/KAFKA/KIP-1099%3A+Extend+kafka-consumer-groups+command+line+tool+to+support+new+consume
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-15284?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kirk True reopened KAFKA-15284:
---
Assignee: Kirk True
> Implement ConsumerGroupProtocolVersionResolver to determine consumer gr
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
When I create a new topic in source cluster with few messages, the new
topic will be replicated successfully to target cluster in few seconds.
Then I create a consumer group in source, consume 1 message in source, this
consumer group will also be replicated successfully to target cluster.
Current
Chris Egerton created KAFKA-17493:
-
Summary: Sink connector-related OffsetsApiIntegrationTest suite
test cases failing more frequently with new consumer/group coordinator
Key: KAFKA-17493
URL: https
Kirk True created KAFKA-17338:
-
Summary: Add validation to ConsumerConfig to prevent using
partition assignors with CONSUMER group protocol
Key: KAFKA-17338
URL: https://issues.apache.org/jira/browse/KAFKA-17338
Kirk True created KAFKA-17337:
-
Summary: Make CONSUMER group protocol default
Key: KAFKA-17337
URL: https://issues.apache.org/jira/browse/KAFKA-17337
Project: Kafka
Issue Type: Task
using.
> Implement ConsumerGroupProtocolVersionResolver to determine consumer group
> protocol
> ---
>
> Key: KAFKA-15284
> URL: https://issues.apache.org/jira/browse/KAFKA-1528
Greg Harris created KAFKA-17232:
---
Summary: MirrorCheckpointConnector does not generate task configs
if initial consumer group load times out
Key: KAFKA-17232
URL: https://issues.apache.org/jira/browse/KAFKA-17232
[
https://issues.apache.org/jira/browse/KAFKA-17047?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Jacot resolved KAFKA-17047.
-
Fix Version/s: 3.9.0
Resolution: Fixed
> Refactor Consumer group and shared classes w
Apoorv Mittal created KAFKA-17047:
-
Summary: Refactor Consumer group and shared classes with Share to
modern package
Key: KAFKA-17047
URL: https://issues.apache.org/jira/browse/KAFKA-17047
Project
[
https://issues.apache.org/jira/browse/KAFKA-16822?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Jacot resolved KAFKA-16822.
-
Fix Version/s: 3.9.0
Resolution: Fixed
> Abstract consumer group in coordinator to sh
Apoorv Mittal created KAFKA-16822:
-
Summary: Abstract consumer group in coordinator to share
functionality with share group
Key: KAFKA-16822
URL: https://issues.apache.org/jira/browse/KAFKA-16822
ore subscription model for consumer group in group state
> --
>
> Key: KAFKA-16587
> URL: https://issues.apache.org/jira/browse/KAFKA-16587
> Project: Kafka
> Issue Type: Sub-task
Edoardo Comar created KAFKA-16622:
-
Summary: Mirromaker2 first Checkpoint not emitted until consumer
group fully catches up once
Key: KAFKA-16622
URL: https://issues.apache.org/jira/browse/KAFKA-16622
Ritika Reddy created KAFKA-16587:
Summary: Store subscription model for consumer group in group state
Key: KAFKA-16587
URL: https://issues.apache.org/jira/browse/KAFKA-16587
Project: Kafka
Assignee: David Jacot
>Priority: Minor
> Fix For: 3.8.0
>
>
> It should be possible to upgrade an existing generic group to a new consumer
> group, in case it was using either the previous generic protocol or manual
> partition assignment and
ics evenly among consumer group
>
>
> Key: KAFKA-16277
> URL: https://issues.apache.org/jira/browse/KAFKA-16277
> Project: Kafka
> Issue Type: Bug
>
Cameron Redpath created KAFKA-16277:
---
Summary: CooperativeStickyAssignor does not spread topics evenly
among consumer group
Key: KAFKA-16277
URL: https://issues.apache.org/jira/browse/KAFKA-16277
Calvin Liu created KAFKA-16250:
--
Summary: Consumer group coordinator should perform sanity check on
the offset commits.
Key: KAFKA-16250
URL: https://issues.apache.org/jira/browse/KAFKA-16250
Project
Andrew Schofield created KAFKA-16243:
Summary: Idle kafka-console-consumer with new consumer group
protocol preemptively leaves group
Key: KAFKA-16243
URL: https://issues.apache.org/jira/browse/KAFKA-16243
; Namboodiri, Vishnu ;
Mudlapur, Rajesh ; Reddy, Thanmai
Subject: RE: Kafka consumer group crashing and not able to consume once service
is up
Hi Philip,
Are you expecting logs from subscriber from our service please do let me know.
Thanks,
Santhosh Aditya
From: Marigowda, Santhosh Aditya
Sent
, Thanmai
Subject: RE: Kafka consumer group crashing and not able to consume once service
is up
Hi Philip, Please find the service logs(Subscriber logs). We don’t see any
logs-related issues with consumer.
Kafka consumer configuration
kafka-consumer = {
server= "10.221.10
..@in.unisys.com>; Mudlapur, Rajesh <
> rajesh.mudla...@au.unisys.com>; Reddy, Thanmai ;
> Marigowda, Santhosh Aditya
> *Subject:* RE: Kafka consumer group crashing and not able to consume once
> service is up
>
>
>
> Hi Philip,
>
> Thanks for your queries, Please
Hi Santhosh,
Your problem statement confuses me a bit (apologize). You mentioned "if one
of the kafka consumer(Service)" - Do you have a single member consumer
group? Could you elaborate on the setup a bit? Did you also mean after
restarting the "service", the service was not
1 - 100 of 780 matches
Mail list logo
