I’m not facing some problems excepted having the best infrastructure and performance/cost ratio.
Actually, I’ve 0 ElasticSearch because I use Toshi and Sonic (depending of the project).
A few years ago, I was facing the eternal disk space usage/provisioning issue with ElasticSearch and I try to avoid having it again.
My actual workaround is a scheduled job running each 3 days doing:
stop sonarqube
delete data/es6 or data/es7 directory (depending of the version)
start sonarqube
It’ll be better to have the possibility to use an alternative to ElasticSearch or having the possibility to link SonarQube (also community edition) to an external ElasticSearch cluster
Note that, when you drop the es directory, Elasticseach indexes are built again and it should result in the same situation as before. The size of the indexes depends on the usage you make of your SonarQube instance.