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.
screen shots are as below, thanks!:
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.
I think you’re right, @Colin, the discrepancy comes from the fact that we interpret the byte amount as GB and not GiB. Using that notation, the parameter -Xmx5G does specify a size of 5.4 GB.
I don’t think there’s anything to do.
This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.