日志中经常看到的Kafka FETCH_SESSION_ID_NOT_FOUND

Posted 2023-03-10

【中文标题】日志中经常看到的Kafka FETCH_SESSION_ID_NOT_FOUND

【英文标题】：Kafka FETCH_SESSION_ID_NOT_FOUND often seen in logs

【发布时间】：2020-01-09 12:30:40

【问题描述】：

运行 Kafka 2.3.0、Kafka 客户端 2.1.1，我的经纪人不断输出以下日志：

[2019-09-06 15:18:03,596] INFO [ReplicaFetcher replicaId=1, leaderId=0, fetcherId=0] Node 0 was unable to process the fetch request with (sessionId=1458702821, epoch=538): FETCH_SESSION_ID_NOT_FOUND. (org.apache.kafka.clients.FetchSessionHandler)
[2019-09-06 15:21:11,145] INFO [GroupMetadataManager brokerId=1] Removed 0 expired offsets in 1 milliseconds. (kafka.coordinator.group.GroupMetadataManager)
[2019-09-06 15:22:33,737] INFO [ReplicaFetcher replicaId=1, leaderId=0, fetcherId=0] Node 0 was unable to process the fetch request with (sessionId=1917353656, epoch=538): FETCH_SESSION_ID_NOT_FOUND. (org.apache.kafka.clients.FetchSessionHandler)
[2019-09-06 15:27:03,768] INFO [ReplicaFetcher replicaId=1, leaderId=0, fetcherId=0] Node 0 was unable to process the fetch request with (sessionId=404608404, epoch=538): FETCH_SESSION_ID_NOT_FOUND. (org.apache.kafka.clients.FetchSessionHandler)
[2019-09-06 15:31:11,145] INFO [GroupMetadataManager brokerId=1] Removed 0 expired offsets in 1 milliseconds. (kafka.coordinator.group.GroupMetadataManager)
[2019-09-06 15:31:34,313] INFO [ReplicaFetcher replicaId=1, leaderId=0, fetcherId=0] Node 0 was unable to process the fetch request with (sessionId=1690401868, epoch=539): FETCH_SESSION_ID_NOT_FOUND. (org.apache.kafka.clients.FetchSessionHandler)
[2019-09-06 15:36:04,404] INFO [ReplicaFetcher replicaId=1, leaderId=0, fetcherId=0] Node 0 was unable to process the fetch request with (sessionId=1167288700, epoch=538): FETCH_SESSION_ID_NOT_FOUND. (org.apache.kafka.clients.FetchSessionHandler)
[2019-09-06 15:40:34,409] INFO [ReplicaFetcher replicaId=1, leaderId=0, fetcherId=0] Node 0 was unable to process the fetch request with (sessionId=2135343705, epoch=538): FETCH_SESSION_ID_NOT_FOUND. (org.apache.kafka.clients.FetchSessionHandler)
[2019-09-06 15:41:11,145] INFO [GroupMetadataManager brokerId=1] Removed 0 expired offsets in 1 milliseconds. (kafka.coordinator.group.GroupMetadataManager)
[2019-09-06 15:45:04,930] INFO [ReplicaFetcher replicaId=1, leaderId=0, fetcherId=0] Node 0 was unable to process the fetch request with (sessionId=1735853846, epoch=539): FETCH_SESSION_ID_NOT_FOUND. (org.apache.kafka.clients.FetchSessionHandler)
[2019-09-06 15:49:35,018] INFO [ReplicaFetcher replicaId=1, leaderId=0, fetcherId=0] Node 0 was unable to process the fetch request with (sessionId=599232284, epoch=538): FETCH_SESSION_ID_NOT_FOUND. (org.apache.kafka.clients.FetchSessionHandler)

大量的 FETCH_SESSION_ID_NOT_FOUND 表示什么？有什么办法可以补救呢？

我的一半消费者群体不消费任何东西，并产生包含大量FETCH_SESSION_ID_NOT_FOUND 行的日志。

【问题讨论】：

@Gary Russell 你能回答这个问题吗，即使我看到了这个错误

确切的问题是什么？

我看到了同样的错误...你看到了什么？

不幸的是我从来没有真正解决过这个问题，不知何故随着 Kafka 的更新问题消失了！

这也不是错误，甚至不是警告，而是信息。所以最好忽略它，除非你有真正的问题

【参考方案1】：

如 cmets 中所述，此问题已通过更新 Kafka 得到解决。

（就该用户而言，这完全是个问题）。如果您有其他症状的问题，则可能是不同的情况，因此请使用不同的问题。