SonarQube: Unrecoverable indexation failures - sonarqube

I'm using SonarQube as a static code analyzer tool and it was working fine. Suddenly it started giving this error - Unrecoverable indexation failures.
I have checked the Sonar log and from es.log I can see this error -
2020.05.13 12:04:25 WARN es[][o.e.c.r.a.DiskThresholdMonitor] high disk watermark [90%] exceeded on
[tsxLSmcQQn2gUd1KfwDGmg][sonarqube][C:\sonarqube-7.8\data\es6\nodes\0]
free: 10.2gb[5.1%], shards will be relocated away from this node
It seems some space issue but since I have 10 GB space left then why it is causing an issue.
How this issue can be fixed without increasing the Hard disk space.

I also meet this error, and my disk has 10GB space left.
then I restart sonarqube, question has solved.
but es.log still has WARN log.
So I think increasing disk space is the only way...
or you can use Treesize.exe to find and delete some unusing file.

Related

Elastic search on Windows - Error - Native memory allocation (mmap) failed

We are running Elastic Search 7.13.2 on a windows server. This was running but suddenly the the ES.bat file is returning an error as below. I have verified that there is no Memory overload in the server. The system has 16 GB RAM, which is 50 percent or less occupied. The free Disk space was > 25GB. Any idea why this error comes up?
I tried to reduce the Heap memory to 4 GB, i created a file named jvm.options inside the jvm.options.d folder and added the below lines, but this doesnt seem to take effect. Any clue on whats going on?
jvm.options file content as below
-Xmx4g
-Xms4g

Increase memory in SpringToolSuite v4.0.1

I'm unable to increase the memory for the app, and app keeps its default 1Gb of heap.
Seems the settings in SpringToolSuite4.ini (what used to be STS.ini) are being ignored.
Putting the "-Xmx" configuration BEFORE the "-startup" seems to resolve the problem.

Xamarin.Forms Java.exe exited with code 1

I've seen a few people encounter this issue with the heap size, which seems to be the issue in my case:
2> Could not reserve enough space for 1048576KB object heap (TaskId:336)
I tried manually setting it to 1G:
Got the same error, realised the space required is actually greater than 1G (it's about 1.04GB), so I set it to 2G. But this just escalated the error:
1> Could not reserve enough space for 2097152KB object heap (TaskId:305)
I thought I'd go nuclear and just set it to 10G, but then I got a different error saying it failed to create the Java VM.
In all honesty, I don't actually know what these mean, I'm just following along based on research of other SO and Xamarin Forums posts. Can anyone explain to me why I'm seeing these errors and how I can fix them?
Notes based on other questions: It's on debug, not release, and I don't have ProGuard ticked.
Steps to fix:
Select 64-bit Java SDK (as per instructions)
Set heap size to 5G (as per screenshot in question)
Built and ran successfully after this.

Kibana stops showing data after a while. Logs too big?

I'm running PALallax, which is a custom version of Kibana / ElasticSearch for Palo Alto firewalls. I have it installed on CentOS 7 with more than enough resources (4 processors, 16GB of RAM). It works fine - however, almost every single day, half way through, Kibana will stop showing results and end up with the dreaded "no results found". I know it works, though. The log file continues to grow (which is big, by the way - about 11GB half way through the day). No matter what I do, I can't get any information to display until I delete the log and indices files on the server and reboot - then it starts working again.
I've looked through logs all around the system and can't figure out what is going on. I'm not an Linux expert, so unfortunately I've run out of ideas and have nothing else to try. I've spent countless days googling different things and haven't been able to isolate any specific problem in the logs.
Any suggestions on where to look? Are my logs too big? I can see that I'm not running out of RAM while this is happening. I always have it set for 'last hour' worth of data, set to auto-refresh every 5 minutes.
Monitor the free disk space and set up automatic deletion of old indices to avoid running out of disk space.

Error occurred during initialization of VM Could not reserve enough space for object heap errorlevel=1

On launching Jmeter, getting below error:
Error occurred during initialization of VM Could not reserve enough space for object heap errorlevel=1.
Please help me to resolve this. I am using laptop with 4GB RAM, 64-bit OS, intel i-5 core.
There could be a lot of processes running in your laptop. That is why you get this error.
Stop all the unwanted programs.
Check the HEAP size setting in JMeter.bat file. Reduce it (128, 512, 1024..)
You need to do the following.
Go to JMETER_HOME/bin folder
Open "jmeter.bat" (assuming you are using windows)
Check "set HEAP=-Xms512m -Xmx512m" (check the heap size- change accordingly)
Update, Close and Relaunch JMeter
You might need more heap for simulating more load.

Resources