一、問題描述
今天開發了一個kafka消費者數據接收的功能，基本過程為分別啟動本地的kafka服務和代碼程序，在服務端手動發送消息，代碼來進行接收消費。經測試，代碼功能正常，但是再接收到一條kafka消息之后，便開始在后台瘋狂打印日志，如圖：
... .2020-08-26 17:00:37.651 com.hikvision.js.facecompare.dao.CaptureFaceInfoDAO.insert DEBUG - <== Updates: 1 .2020-08-26 17:00:37.651 org.mybatis.spring.SqlSessionUtils DEBUG - Closing non transactional SqlSession [org.apache.ibatis.session.defaults.DefaultSqlSession@76f8de1f] .2020-08-26 17:00:37.652 com.hikvision.js.facecompare.service.impl.KafkaConsumerListener INFO - 一條kafka消息已經入庫：1598432437652 .2020-08-26 17:00:37.658 org.apache.kafka.clients.consumer.internals.ConsumerCoordinator DEBUG - Committed offset 3 for partition SNAP_IMAGE_INFO_TOPIC-0 .2020-08-26 17:00:37.912 org.apache.kafka.clients.consumer.internals.AbstractCoordinator DEBUG - Received successful heartbeat response. .2020-08-26 17:00:38.654 org.apache.kafka.clients.consumer.internals.ConsumerCoordinator DEBUG - Committed offset 3 for partition SNAP_IMAGE_INFO_TOPIC-0 .2020-08-26 17:00:39.654 org.apache.kafka.clients.consumer.internals.ConsumerCoordinator DEBUG - Committed offset 3 for partition SNAP_IMAGE_INFO_TOPIC-0 .2020-08-26 17:00:40.654 org.apache.kafka.clients.consumer.internals.ConsumerCoordinator DEBUG - Committed offset 3 for partition SNAP_IMAGE_INFO_TOPIC-0 .2020-08-26 17:00:40.910 org.apache.kafka.clients.consumer.internals.AbstractCoordinator DEBUG - Received successful heartbeat response. .2020-08-26 17:00:41.657 org.apache.kafka.clients.consumer.internals.ConsumerCoordinator DEBUG - Committed offset 3 for partition SNAP_IMAGE_INFO_TOPIC-0 .2020-08-26 17:00:42.656 org.apache.kafka.clients.consumer.internals.ConsumerCoordinator DEBUG - Committed offset 3 for partition SNAP_IMAGE_INFO_TOPIC-0 .2020-08-26 17:00:43.656 org.apache.kafka.clients.consumer.internals.ConsumerCoordinator DEBUG - Committed offset 3 for partition SNAP_IMAGE_INFO_TOPIC-0 ...
網上查詢得知，需要設置對應類的日志打印級別，設置之后還是不行。
二、解決方法
在idea全局搜索ConsumerCoordinator 類發現，不止一個jar包中包含這個類，仔細分析發現其中一個包是我在代碼調試過程中手動添加的外部jar包，這個jar包已經沒什么用了，於是手動將該包移除，重新啟動消費端程序，再次接受kafka消息，恢復正常，因此日志頻繁打印的原因應該是兩個jar包沖突。