Hi, community:
The metrics are all started with `pulsar_`, so that both users and
operators can quickly find the metrics of the entire system through
this prefix. However, due to some other reasons, it was found that
`topic_load_times` was missing the prefix, so want to get it right.
In the
Hi Lari,
Generally I agree with your points. The cherry-picking criteria is
very ambiguous and not clear. I also found some unexpected
cherry-picks recently. For example, #16014 [1] actually breaks the
compatibility of determining whether to use a TLS service URL for a
built-in Pulsar client. Thou
Do we need to have https://github.com/apache/bookkeeper/pull/3979
in the 3.0.1 release? since it's a critical issue for BookKeeper.
Thanks,
Penghui
On Sun, Jun 11, 2023 at 12:07 AM Enrico Olivelli
wrote:
> I have reported a few problems about ExtensibleLoadManagerImpl (PIP-192) on
> k8s.
>
> I
I agree with you. wasAutoCreated seems a bit like a patch in light of the
recent issues.
On Fri, Jun 9, 2023 at 9:03 AM Michael Marshall
wrote:
> > In general, these problems hint to me that we need better definitions
> > for "system" and "special" topics that break the rules of auto created
>