[
https://issues.apache.org/jira/browse/KAFKA-10753?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17237795#comment-17237795
]
dengziming commented on KAFKA-10753:
------------------------------------
[~Jack-Lee] I think we should first reach a consensus on how this should be
fixed, or we just ignore it.
# If we just add a simple `time>0` check, there are so many configs to be
checked.
# If we alter the backoff in `KafkaConsumer.pollForFetches`, it is a
non-trivial fix, we can create another Jira to track it.
> 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
> Attachments: KAFKA-10753.patch
>
>
> 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)
