[
https://issues.apache.org/jira/browse/KAFKA-10753?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17237237#comment-17237237
]
shiqihao commented on KAFKA-10753:
----------------------------------
Sorry for not being clear enough. The key point of this issue is: IF AND ONLY
IF AUTO_COMMIT_INTERVAL_MS_CONFIG == 0,
auto-commit will execute continuously, so that CPU resources will be exhausted.
If AUTO_COMMIT_INTERVAL_MS_CONFIG > 0, the program runs well.
i.e. as
[lqjacklee|https://issues.apache.org/jira/secure/ViewProfile.jspa?name=Jack-Lee]
shows: if timeoutMs == 0, startMs == deadlineMs, the methods use Timer.reset()
e.g. auto-commit or heartbeat will exhaust CPU resources.
> check if ConsumerConfig.AUTO_COMMIT_INTERVAL_MS_CONFIG > 0
> -----------------------------------------------------------
>
> Key: KAFKA-10753
> URL: https://issues.apache.org/jira/browse/KAFKA-10753
> Project: Kafka
> Issue Type: Improvement
> Components: consumer
> Reporter: shiqihao
> Assignee: lqjacklee
> Priority: Minor
>
> I accidentally set ConsumerConfig.AUTO_COMMIT_INTERVAL_MS_CONFIG = 0, CPU
> running at 100%.
> Could we add a check if ConsumerConfig.AUTO_COMMIT_INTERVAL_MS_CONFIG > 0
> while start consumer?
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
