[ https://issues.apache.org/jira/browse/KAFKA-10753?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17239063#comment-17239063 ]
shiqihao commented on KAFKA-10753: ---------------------------------- hi [lqjacklee|https://issues.apache.org/jira/secure/ViewProfile.jspa?name=Jack-Lee] , this problem cannot be replayed by unit test, you can simply initialize a kafka consumer and start it. Then using top -o cpu command, you will find kafka process and comsumer process is using too much CPU. > 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)