Sonar generates huge CPU spikes every 5-10 seconds when there's no config file #20
Description
What happened
When there's no sonar.conf file, sonar restarts every 10 seconds, creating huge CPU spikes that can disrupt a print. It shows this message when happening:
WARN: No configuration file found ... INFO: Using fallback setup ...
This message is misleading because it gives the impression that Sonar will use the fallback config, but it's not. The fallback config is the one in the resources directory and it has this line:
enable: false
I would expect the service to stop, but it's still restarting every 5-10 seconds.
What did you expect to happen
I expect the service to stop for good when there's no config file. If not, then I would expect it to show a better warning than the current one.
How to reproduce
Just delete the sonar.conf file.
Additional information
No response