High Disk Watermark

SonarQube Server / Community Build
1

Hello There,

We are using Sonarqube 10.7 Community Edition. While installing we have faced the issue of High Disk Watermark where SonarQube server does not start if disk space utilization is above 90%. If we reduce the disk space utilization below 90% then it works fine.

We have few queries if anyone can help answer it.

  1. Does SonarQube 10.7 requires minimum 10% free disk space irrespective of the free disk space in GB? Like in our case, free disk space is 4.2% but that translates to 17.3 GB which should be more than enough for SonarQube to run smoothly.

  2. If answer to above is yes, is there any way where we can update the properties, or any settings reduce the percentage of free disk space required?

  3. Assuming if we have reduced the disk space below 90%, started SonarQube, now after a while if disk space utilization crosses over 90% then what will happen? Does SonarQube server stops working or it will still work giving some warning.

**2025.02.28 10:16:37 INFO  es[][o.e.c.r.a.AllocationService] current.health="RED" message="Cluster health status changed from [YELLOW] to [RED] (reason: [reconcile-desired-balance])." previous.health="YELLOW" reason="reconcile-desired-balance"**
**2025.02.28 10:17:01 WARN  es[][o.e.c.r.a.DiskThresholdMonitor] flood stage disk watermark [95%] exceeded on [wd3RRIMnS7iTImH-Am81dQ][sonarqube][/opt/tibco/devops/sonarqube/sonarqube-10.7.0.96327/data/es8] free: 17.3gb[4.2%], all indices on this node will be marked read-only**
2025.02.28 10:17:37 INFO  web[][o.s.s.e.IndexCreator] Create mapping metadatas
2025.02.28 10:18:07 ERROR web[][o.s.s.p.Platform] Background initialization failed. Stopping SonarQube
org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'jdk.internal.loader.ClassLoaders$AppClassLoader@5ffd2b27-org.sonar.server.es.IndexCreator': Initialization of bean failed; nested exception is org.sonar.server.es.ElasticsearchException: Fail to execute es requestES get request for key 'dbVendor' on index 'metadatas'
''
''       
"
        **Suppressed: org.elasticsearch.client.ResponseException: method [GET], host [http://localhost.localdomain:9002], URI [/metadatas/_doc/dbVendor?stored_fields=value], status line [HTTP/1.1 503 Service Unavailable]**
{"error":{"root_cause":[{"type":"no_shard_available_action_exception","reason":"No shard available for [get [metadatas][dbVendor]: routing **[null]]"}],"type":"no_shard_available_action_exception","reason":"No shard available for [get [metadatas][dbVendor]: routing [null]]"},"status":503}**
2

Hi,

Welcome to the community!

First, SonarQube 10.7 is EOL. You should upgrade at your earliest convenience to SonarQube Community Build 25.2.

This is actually a requirement of Elasticsearch, which SonarQube uses under the covers. And yes, unfortunately, its a percentage requirement, regardless of how much free disk 4.2% actually translates to.

Sorry, no.

Yes, SonarQube shuts down. I believe the warnings come at lower watermarks, perhaps 85%?

 
HTH,
Ann

1 Like
3

Thank you for the update Ann.