Jvm max heap size on system info page not equal to config in sonar.properties

SonarQube
,
#1

Hi all,
I upgrade my sonarqube data center from 8.9.6 to 9.4.0 and found search node ‘JVM Heap Max’ not equal to value in sonar.properties. the should be 5GB, but on page it was 5.4GB.
The value of ’JavaOptsSearch‘ on my search node is ‘-server -Xms5G -Xmx5G -XX:+HeapDumpOnOutOfMemoryError’
I also check actually jvm heap max size on search node, it was exactlly 5GB.

Any idea?

Thanks!
Deimos

#3

screen shots are as below, thanks!:

1
11002×332 6.8 KB

2
21230×248 79.8 KB

3
3840×497 12.2 KB

#4

It looks like there’s a conversion going on between gibibyte and gigabyte that’s causing the discrepancy (while everything is probably as expected). I’ve flagged the thread internally to see if there’s anything we want to do about this.