GitHub user justin-lathrop added a comment to the discussion: Pulsar upgrade to
3.0.5 causes prometheus metrics timeouts on brokers
cgroup v1 and `grep cgroup /proc/filesystems` shows only `nodev cgroup`.
```
pulsar@pulsar-broker-0:/pulsar$ uname -a
Linux pulsar-broker-0 3.10.0-1160.95.1.el7.x86_64 #1 SMP Mon Jul 24 13:59:37
UTC 2023 x86_64 x86_64 x86_64 GNU/Linux
```
```
pulsar@pulsar-broker-0:/pulsar$ java -XshowSettings:system -version
Operating System Metrics:
Provider: cgroupv1
Effective CPU Count: 36
CPU Period: 100000us
CPU Quota: -1
CPU Shares: 204us
List of Processors, 36 total:
0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27
28 29 30 31 32 33 34 35
List of Effective Processors, 36 total:
0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27
28 29 30 31 32 33 34 35
List of Memory Nodes, 1 total:
0
List of Available Memory Nodes, 1 total:
0
Memory Limit: Unlimited
Memory Soft Limit: Unlimited
Memory & Swap Limit: Unlimited
Maximum Processes Limit: Unlimited
openjdk version "17.0.11" 2024-04-16
OpenJDK Runtime Environment Temurin-17.0.11+9 (build 17.0.11+9)
OpenJDK 64-Bit Server VM Temurin-17.0.11+9 (build 17.0.11+9, mixed mode,
sharing)
```
Updating the `PULSAR_MEM` to have additionally `-XX:ActiveProcessorCount=1`
then restarting the pulsar-broker sts continues to give the same metrics
timeout.
GitHub link:
https://github.com/apache/pulsar/discussions/22897#discussioncomment-9799000
----
This is an automatically sent email for [email protected].
To unsubscribe, please send an email to: [email protected]
