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

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

dengziming commented on pull request #7761: KAFKA-9246: Update Heartbeat 
timeout when ConsumerCoordinator commit offset
URL: https://github.com/apache/kafka/pull/7761
 
 
   GroupCoordinator will invoke completeAndScheduleNextHeartbeatExpiration to 
update the expires when handleCommitOffsets, so the consumer can also update 
the heartbeat timeout of ConsumerCoordinator when sending OffsetCommitRequest 
to reduce Heartbeat Request.
   
   ### Committer Checklist (excluded from commit message)
   - [ ] Verify design and implementation 
   - [ ] Verify test coverage and CI build status
   - [ ] Verify documentation (including upgrade notes)
   
 
----------------------------------------------------------------
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


> Update Heartbeat timeout when ConsumerCoordinator commit offset
> ---------------------------------------------------------------
>
>                 Key: KAFKA-9246
>                 URL: https://issues.apache.org/jira/browse/KAFKA-9246
>             Project: Kafka
>          Issue Type: Improvement
>          Components: clients
>            Reporter: dengziming
>            Priority: Minor
>             Fix For: 2.2.0, 2.3.0
>
>
> when a consumer sends OffsetCommitRequest, it also can be treated as a 
> Heartbeat and the `GroupCoordinator` will invoke 
> `completeAndScheduleNextHeartbeatExpiration`  to update the expires when 
> handleCommitOffsets. 
> so we can also update the heartbeat expires of ConsumerCoordinator when send 
> OffsetCommitRequest to reduce Heartbeat Request.



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

Reply via email to