为什么在卡夫卡使用FETCH_SESSION_ID_NOT_FOUND?

时间:2020-02-11 23:23:10

标签: apache-kafka

我有很多FETCH_SESSION_ID_NOT_FOUND

INFO [ReplicaFetcher replicaId=2, leaderId=1, fetcherId=2] Node 1 was unable to process the fetch request with (sessionId=1229568311, epoch=511): FETCH_SESSION_ID_NOT_FOUND. (org.apache.kafka.clients.FetchSessionHandler)
INFO [ReplicaFetcher replicaId=2, leaderId=1, fetcherId=5] Node 1 was unable to process the fetch request with (sessionId=136816338, epoch=504): FETCH_SESSION_ID_NOT_FOUND. (org.apache.kafka.clients.FetchSessionHandler)
INFO [ReplicaFetcher replicaId=2, leaderId=0, fetcherId=2] Node 0 was unable to process the fetch request with (sessionId=311282207, epoch=569): FETCH_SESSION_ID_NOT_FOUND. (org.apache.kafka.clients.FetchSessionHandler)
...

我读了Kafka: Continuously getting FETCH_SESSION_ID_NOT_FOUNDHow to check the actual number of incremental fetch session cache slots used in Kafka cluster?

目前,我们刚刚获得了有关Burrow的滞后指标。

我的问题:

1,有人可以解释为什么我有这么多FETCH_SESSION_ID_NOT_FOUND吗?这是什么意思?我以前没买。

有些消费者发送太多请求?还是领导人总是连任?

我不知道。可以给我更多细节吗?

2,如果是因为某些消费者发送了太多请求,那么如何识别这些消费者?

谢谢

0 个答案:

没有答案