I have several context-related questions:
1. When a topic fails to load, what happens exactly at that stage? Does it switch over to another broker? Is there a retry on the current broker? 2. Is there a way to provide a gauge showing how many topics are unloaded due to non-recoverable error? Or maybe topics unloaded but are currently retrying? 3. I presume granularity is per broker. The scenario is: I setup an alert on rate of this counter > 0 ? Could it be a transient error thus I’m alerted on something less important? How do you see this in production I guess is the question. Thanks! Asaf On 19 Dec 2022 at 10:19:39, Jiuming Tao <jm...@streamnative.io.invalid> wrote: > Hello pulsar community, > > I've opened `PIP-231: Add metric for topic load failed` to discuss. > > Motivation: > Currently, we have topic_load_times > <https://pulsar.apache.org/docs/next/reference-metrics/#broker-metrics> > metric > to tracking how long a topic load succeed. > But when loading a topic, there are may have some chances the topic load > failed due to MetadataStore or Bookkeeper, and we don't have related > metrics to track it. > > For more details, please read the PIP at > https://github.com/apache/pulsar/issues/18979 > I'm looking forward to hearing what you think. > > Thanks, > Tao Jiuming >
