Lari Hotari

> However, RFC 8414 defines `/.well-known/oauth-authorization-server` as the default, and some users may want to configure a different path. > https://datatracker.ietf.org/doc/html/rfc8414#section-3 > This PR makes the authorization server metadata path...

@miton18 Please rebase this PR (or merge origin/master) and add a description

> ### Reproducing the issue > When conducting consumption performance pressure tests with a relatively large number of consumers per partition (over 1000), consumption imbalance will occur: the consumption speed...

> 3.0.10 > jdk17 > client 3.0.10 @g0715158 Please retest with Pulsar 4.1.2 version, running on Java 21.0.9 (or newer). Pulsar 4.1.x comes with ["PIP-430: Pulsar Broker Cache Improvements: Refactoring...

> Currently, my goal is to identify the root cause of partition imbalance in version 3.0.10. @g0715158 In the OSS project, we don't maintain specific versions such as 3.0.10. 3.0.x...

In dispatching, I have had some doubts of the source of imbalance in this logic: https://github.com/apache/pulsar/blob/ea56ada4f3985c93b93c64d1361b3111cd98a37f/pulsar-broker/src/main/java/org/apache/pulsar/broker/service/AbstractDispatcherMultipleConsumers.java#L77-L226

> [@lhotari](https://github.com/lhotari) Thank you so much for your help! When I ran pressure tests with 1KB small messages, the performance was solid and stable—only partition imbalance occurred, with a TPS...

> Other metrics appear normal, and no thread blockages were detected in the broker thread dumps. What metrics are you checking? If you want to get proper performance, you should...

Please also check #24695

> [@lhotari](https://github.com/lhotari) We have not enabled this parameter as managedLedgerMaxReadsInFlightSizeInMB=0. Currently, the broker has 20GB of heap memory and 40GB of off-heap memory available. Would it be appropriate for us...