hi
If the sole objective is to prevent a specific consumer from reading
records, consider utilizing quotas to limit read throughput based on the
client ID. While this approach may not provide partition-level control, it
effectively allows administrators to regulate data flow for individual
consume
Hi,
Just pushed the PoC making it working based on spring kafka listener
container. The main point is about using ConsumerRebalanceListener to watch
for changed in the partition the consumer member is bound to, and take
advantage of spring container to make it pausing. Relevant code here
https://g
Hi there,
The PoC is here https://github.com/asorian0/kafka-admin-poc. I just found
that I was using kafka 3 instead of 4 and it seems that changes in
MemberToRemove are not working with the latest major. Are you aware about
what could have been changed?
The actual error is:
org.apache.kafka.com
Hi Tsai,
Thanks for your quick response and sorry for the late reply, i'm involved
in some other investigations that are consuming my time, but i'm going to
move forward on this one from now on.
Your questions are really pointing the spot though, and guess i kinda
anticipated them in the last pie
hi Armando
Thanks for your question and contribution. Few questions are listed below.
PTAL
> I'm working in a java service that allows managing consumer group's
members, specially to pause/resume them on demand.
Out of curiosity, could you elaborate on how the
removeMembersFromConsumerGroup meth
Hi there,
I'm working in a java service that allows managing consumer group's
members, specially to pause/resume them on demand. After checking here and
there it seems that the actual AdminClient makes this feasible through
removeMembersFromConsumerGroup method [
https://kafka.apache.org/38/javado
