Hey guys!

I had a 52GB solr-8983-console.log on my Solr 5.2.1 Amazon Linux
64-bit box and decided to `cat /dev/null > solr-8983-console.log` to
free space.

The weird thing is that when I checked Sematext I noticed the OS had
freed a lot of memory at the same exact instant I did that.

https://dl.dropboxusercontent.com/u/10240770/disk-space.png

https://dl.dropboxusercontent.com/u/10240770/memory-usage.png

I'm really not very familiar with how the OS allocates memory, but it
seemed weird that truncating a file would actually free some of it.

Any pointers on what I'm missing here would be greatly appreciated.

Best,

Eric Torti

Reply via email to