We have Kafka clusters in three datacenters with Mirror Maker replicating
across three data centers. We are monitoring JMX metrics of our clusters.
I have question regarding FetchRequestPurgatory
(kafka.server:type=FetchRequestPurgatory,name=PurgatorySize), description on
Wiki says "Numb
h brokers are up, after a short while the FetchRequestPurgatory
starts to grow indefinitely on the leader (detectable via a heap dump and
also via the "FetchRequestPurgatory"."PurgatorySize" JMX metric),
eventually leading to an OOM error. When one of the brokers is shut down,
the
András Serény
wrote:
> Hi Kafka users,
>
> we're running a cluster of two Kafka 0.8.1.1 brokers, with a twofold
> replicaton of each topic.
>
> When both brokers are up, after a short while the FetchRequestPurgatory
> starts to grow indefinitely on the leader (detectable vi
Hi Kafka users,
we're running a cluster of two Kafka 0.8.1.1 brokers, with a twofold
replicaton of each topic.
When both brokers are up, after a short while the FetchRequestPurgatory
starts to grow indefinitely on the leader (detectable via a heap dump
and also vi
