GKE Autopilot sonarqube developer version initSys error

SonarQube Server / Community Build
,
1

Hey using sonarqube helm-chart on GKE Autopilot and getting error:

+ vmMaxMapCount=262144
++ sysctl -n vm.max_map_count
+ [[ 65530 -lt 262144 ]]
+ sysctl -w vm.max_map_count=262144
sysctl: setting key "vm.max_map_count", ignoring: Read-only file system
vm.max_map_count = 262144
++ sysctl -n vm.max_map_count
Failed to set initSysctl.vmMaxMapCount
+ [[ 65530 -lt 262144 ]]
+ echo 'Failed to set initSysctl.vmMaxMapCount'
+ exit 1

Saw similar error faced before, but didn’t see any solution.
Any suggestions appreciated!

4

Hello @rahymov, thanks a lot for participating in the community.

We have some strict elasticsearch kernel requirements in order to run SonarQube, could you try to follow this documentation and set initSysctl.enabled=false and initFs.enabled=false ?

Thanks a lot, let me know if this solves the issue.

5

I’ve disabled initSysctl and elasticSearch.bootstrapChecks: false. Did work(sonarqube healthy), but would it be issue or what kinda issues we could face?

6

You should not face any issues now if SonarQube started.

The initSysctl is there to set a vmmaxmap.count kernel parameter required for elasticsearch, if this is too low, SonarQube will not start at all. This means that on the autopilot cluster, parameters are already big enough.

Best regards.

8

Got it, thank you!