Thank you Shawn, Timothy, Emir and Rajani.

Sorry, Shawn, I ended up cropping out the legend but you were right on
your guess.

Indeed, Timothy, this log is completely redundant. Will get rid of it soon.

I'll look into the resources you all pointed out. Thanks!

Best,

Eric Torti

On Wed, Oct 21, 2015 at 8:21 PM, Rajani Maski
<rajani.ma...@lucidworks.com> wrote:
> This details in this link[1] might be of help.
>
> [1]https://support.lucidworks.com/hc/en-us/articles/207072137
>
> On Wed, Oct 21, 2015 at 7:42 AM, Emir Arnautovic <
> emir.arnauto...@sematext.com> wrote:
>
>> Hi Eric,
>> As Shawn explained, memory is freed because it was used to cache portion
>> of log file.
>>
>> Since you are already with Sematext, I guess you are aware, but doesn't
>> hurt to remind you that we also have Logsene that you can use to manage
>> your logs: http://sematext.com/logsene/index.html
>>
>> Thanks,
>> Emir
>>
>> --
>> Monitoring * Alerting * Anomaly Detection * Centralized Log Management
>> Solr & Elasticsearch Support * http://sematext.com/
>>
>>
>>
>>
>> On 20.10.2015 17:42, Shawn Heisey wrote:
>>
>>> On 10/20/2015 9:19 AM, Eric Torti wrote:
>>>
>>>> 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.
>>>>
>>> On that memory graph, the legend doesn't indicate which of the graph
>>> colors represent each of the four usage types at the top -- they all
>>> have blue checkboxes, so I can't tell for sure what changed.
>>>
>>> If the number that dropped is "cached" (which I think is likely) then
>>> everything is working exactly as it should.  The OS had simply cached a
>>> large chunk of the logfile, exactly as it is designed to do, and once
>>> the file was deleted, it stopped reserving that memory and made it
>>> available.
>>>
>>> https://en.wikipedia.org/wiki/Page_cache
>>>
>>> Thanks,
>>> Shawn
>>>
>>>

Reply via email to