[ 
https://issues.apache.org/jira/browse/KAFKA-9741?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17063708#comment-17063708
 ] 

ASF GitHub Bot commented on KAFKA-9741:
---------------------------------------

mjsax commented on pull request #8325: KAFKA-9741: Update ConsumerGroupMetadata 
before calling onPartitionsRevoked()
URL: https://github.com/apache/kafka/pull/8325
 
 
   If partitions are revoked, an application may want to commit the current 
offsets.
   
   Using transactions, committing offsets would be done via the producer 
passing in the current `ConsumerGroupMetadata`. If the metadata is not updates 
before the callback, the call to `commitTransaction(...)` fails as and old 
generationId would be used.
   
   Call for review @ableegoldman @abbccdda @guozhangwang @hachikuji 
   
   \cc @mumrah (not sure if this is a blocker for 2.5 or not)
 
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


> ConsumerCoordinator must update ConsumerGroupMetadata before calling 
> onPartitionsRevoked()
> ------------------------------------------------------------------------------------------
>
>                 Key: KAFKA-9741
>                 URL: https://issues.apache.org/jira/browse/KAFKA-9741
>             Project: Kafka
>          Issue Type: Bug
>          Components: consumer
>    Affects Versions: 2.5.0
>            Reporter: Matthias J. Sax
>            Assignee: Matthias J. Sax
>            Priority: Critical
>
> If partitions are revoked, an application may want to commit the current 
> offsets.
> Using transactions, committing offsets would be done via the producer passing 
> in the current `ConsumerGroupMetadata`. If the metadata is not updates before 
> the callback, the call to `commitTransaction(...)` fails as and old 
> generationId would be used.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Reply via email to