标签：java kafka heard sessionid session NotificationHookConsumer apache org poll

一、报错日志

2022-07-21 09:12:42,274 WARN  - [main-SendThread(hadoop01:2181):] ~ Client session timed out, have not heard from server in 34640ms for sessionid 0xff821bd396610617 (ClientCnxn$SendThread:1190)
2022-07-21 09:12:42,819 WARN  - [main-SendThread(hadoop01:2181):] ~ Unable to reconnect to ZooKeeper service, session 0xff821bd396610617 has expired (ClientCnxn$SendThread:1380)
2022-07-21 09:12:42,819 WARN  - [main-EventThread:] ~ Session expired event received (ConnectionState:372)
2022-07-21 09:12:43,323 WARN  - [NotificationHookConsumer thread-0:] ~ Exception in NotificationHookConsumer (NotificationHookConsumer$HookConsumer:550)
org.apache.kafka.clients.consumer.CommitFailedException: Commit cannot be completed since the group has already rebalanced and assigned the partitions to another member. This means that the time between subsequent calls to poll() was longer than the configured max.poll.interval.ms, which typically implies that the poll loop is spending too much time message processing. You can address this either by increasing the session timeout or by reducing the maximum size of batches returned in poll() with max.poll.records.
        at org.apache.kafka.clients.consumer.internals.ConsumerCoordinator.sendOffsetCommitRequest(ConsumerCoordinator.java:813)
        at org.apache.kafka.clients.consumer.internals.ConsumerCoordinator.commitOffsetsSync(ConsumerCoordinator.java:696)
        at org.apache.kafka.clients.consumer.KafkaConsumer.commitSync(KafkaConsumer.java:1418)
        at org.apache.kafka.clients.consumer.KafkaConsumer.commitSync(KafkaConsumer.java:1379)
        at org.apache.atlas.kafka.AtlasKafkaConsumer.commit(AtlasKafkaConsumer.java:106)
        at org.apache.atlas.notification.NotificationHookConsumer$HookConsumer.commit(NotificationHookConsumer.java:909)
        at org.apache.atlas.notification.NotificationHookConsumer$HookConsumer.handleMessage(NotificationHookConsumer.java:819)
        at org.apache.atlas.notification.NotificationHookConsumer$HookConsumer.doWork(NotificationHookConsumer.java:544)
        at kafka.utils.ShutdownableThread.run(ShutdownableThread.scala:82)
        at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
        at java.util.concurrent.FutureTask.run(FutureTask.java:266)
        at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
        at java.lang.Thread.run(Thread.java:748)

二、原因分析

　　我这边写了一个shell脚本，调用Atlas的CURL数据导出接口，从Atlas中导出数据，由于数据量比较大，导出时间就比较长，而Zookeeper这边配置的最小Session过期时间是1个半小时，一旦Session使用超过一个半小时，Session便会失效，从而导致导出数据的缺失，这样Kafka也会跟着报错，无法提交事务

三、解决方案

　　修改Zookeeper的minSessionTimeout、maxSessionTimeout两个参数，单位是毫秒，操作如下：

cd zookeeper安装目录

vim conf/zoo.cfg

修改内容如下：

#最小Session过期时间，设置为1天
minSessionTimeout=86400000
#最大Session过期时间，设置为2天
maxSessionTimeout=172800000

　　完成之后重启ZK即可

标签：java,kafka,heard,sessionid,session,NotificationHookConsumer,apache,org,poll
来源： https://www.cnblogs.com/qq1035807396/p/16500749.html

本站声明： 1. iCode9 技术分享网（下文简称本站）提供的所有内容，仅供技术学习、探讨和分享；
2. 关于本站的所有留言、评论、转载及引用，纯属内容发起人的个人观点，与本站观点和立场无关；
3. 关于本站的所有言论和文字，纯属内容发起人的个人观点，与本站观点和立场无关；
4. 本站文章均是网友提供，不完全保证技术分享内容的完整性、准确性、时效性、风险性和版权归属；如您发现该文章侵犯了您的权益，可联系我们第一时间进行删除；
5. 本站为非盈利性的个人网站，所有内容不会用来进行牟利，也不会利用任何形式的广告来间接获益，纯粹是为了广大技术爱好者提供技术内容和技术思想的分享性交流网站。