[
https://issues.apache.org/jira/browse/KAFKA-17780?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17890533#comment-17890533
]
Kirk True commented on KAFKA-17780:
-----------------------------------
>From my read of the current code in {{{}AbstractHeartbeatRequestManager{}}}’s
>constructor, we set the interval to 0 initially. On the first (and subsequent)
>heartbeat responses, we call {{onResponse()}} and update the interval, if
>needed. This is because, as you mentioned, the heartbeat interval is now a
>server-side configuration.
Does that explanation seem correct, or no?
> Heartbeat interval is not configured in the heartbeatrequest manager
> --------------------------------------------------------------------
>
> Key: KAFKA-17780
> URL: https://issues.apache.org/jira/browse/KAFKA-17780
> Project: Kafka
> Issue Type: Bug
> Components: clients, consumer, kip
> Reporter: Arpit Goyal
> Priority: Critical
> Labels: kip-848-client-support
>
> In the AbstractHeartBeatRequestManager , I observed we are not setting the
> right heartbeat request interval. Is this intentional ?
> [~lianetm] [~kirktrue]
> {code:java}
> long retryBackoffMs = config.getLong(ConsumerConfig.RETRY_BACKOFF_MS_CONFIG);
> long retryBackoffMaxMs =
> config.getLong(ConsumerConfig.RETRY_BACKOFF_MAX_MS_CONFIG);
> this.heartbeatRequestState = new HeartbeatRequestState(logContext,
> time, 0, retryBackoffMs,
> retryBackoffMaxMs, maxPollIntervalMs);
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
