Lari Hotari
04/26/2023, 3:19 PMHi all,
Pulsar doesn't support cgroup v2 which becomes default in Kubernetes v1.25+.
Kubernetes announcement:
https://kubernetes.io/blog/2022/08/31/cgroupv2-ga-1-25/ .
Pulsar issue: https://github.com/apache/pulsar/issues/16601
The impact of this is that the Pulsar load balancer won't have correct
CPU and memory information for making load balancing decisions.
The cloud provider managed Kubernetes services have already switched
to cgroup v2 as the default. This happened in AKS v1.25, GKE v1.26 and
in EKS v1.26.
For GKE, it's possible to keep using cgroup v1 also in GKE v1.26
(https://cloud.google.com/kubernetes-engine/docs/how-to/node-system-config#cgroup-mode-options).
For AKS and EKS, it's unknown whether such a configuration option
exists.
There's a previous attempt in this PR to add cgroup v2 support to
Pulsar: https://github.com/apache/pulsar/pull/16832 . Would it be
possible to continue the work for supporting cgroup v2 in Pulsar
either with the existing PR or a new one?
Who would like to pick up this work?
This is urgent since cgroup v2 is enabled by default for all latest
managed Kubernetes services (AKS v1.25, GKE v1.26 and EKS v1.26).
Regards,
-Lari
Enrico Olivelli
06/09/2023, 9:12 AMEnrico Olivelli
06/09/2023, 9:12 AMEnrico Olivelli
06/09/2023, 9:12 AMEnrico Olivelli
06/09/2023, 9:12 AMEnrico Olivelli
06/09/2023, 9:12 AMHeesung Sohn
06/09/2023, 9:38 AMHeesung Sohn
06/09/2023, 9:40 AMHeesung Sohn
06/09/2023, 5:32 PMLari Hotari
06/21/2023, 9:10 AMLari Hotari
06/22/2023, 1:09 PMExtensibleLoadManagerImplTest.initializeState
is also flaky. Any chances to investigate that? Reported as https://github.com/apache/pulsar/issues/20157 .