I propose to cut the first 2.7.2RC on April 12th.
Is this a good trade off?
Enrico
Il Gio 1 Apr 2021, 22:56 Michael Marshall ha
scritto:
> After discussing this issue in the Pulsar community meeting today, I
> realized that I might not have described the issue well enough. The
> fundamental
After discussing this issue in the Pulsar community meeting today, I
realized that I might not have described the issue well enough. The
fundamental problem is that brokers create 4 metrics for every cursor and
there is no way to disable them. The change to make these metrics optional
has already b
Thank you for your offer, Enrico.
> If you are now blocked, then other users will be blocked as well.
I looked into this more today, and I believe that I am blocked on using
2.7.1. I configured prometheus's server side filtering for the high
cardinality metrics, but my prometheus instance is stil
Michael,
The bugfix releases are usually made monthly based on demand. We can
probably wait 1~2 weeks to see if there are any other fixes to include
before cutting a 2.7.2 release. Does that make sense?
Thanks,
Sijie
On Tue, Mar 30, 2021 at 9:55 PM Michael Marshall
wrote:
> Hi All,
>
> I propo
Michael,
Il giorno mer 31 mar 2021 alle ore 06:55 Michael Marshall
ha scritto:
>
> Hi All,
>
> I propose and request that we release version 2.7.2 to fix a regression
> introduced in 2.7.1.
>
> Pulsar 2.7.1 introduced cursor level metrics without including the ability
> to disable them (https://g
Hi All,
I propose and request that we release version 2.7.2 to fix a regression
introduced in 2.7.1.
Pulsar 2.7.1 introduced cursor level metrics without including the ability
to disable them (https://github.com/apache/pulsar/pull/9618). I recently
discovered the metrics when I created a Pulsar 2
