Re: `cat /dev/null > solr-8983-console.log` frees host's memory

Hi Tim, Should we remove the console appender by default? This is very trappy I guess. On Tue, Oct 20, 2015 at 11:39 PM, Timothy Potter wrote: > You should fix your log4j.properties file to no log to console ... > it's there for the initial getting started experience, but

Re: `cat /dev/null > solr-8983-console.log` frees host's memory

On 10/22/2015 12:24 AM, Shalin Shekhar Mangar wrote: > Should we remove the console appender by default? This is very trappy I guess. The only time we should need console logging is when Solr is run in the foreground, and in that case, it should not be saved to a file, just printed on the

Re: `cat /dev/null > solr-8983-console.log` frees host's memory

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

Re: `cat /dev/null > solr-8983-console.log` frees host's memory

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

Re: `cat /dev/null > solr-8983-console.log` frees host's memory

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,

`cat /dev/null > solr-8983-console.log` frees host's memory

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.

Re: `cat /dev/null > solr-8983-console.log` frees host's memory

You should fix your log4j.properties file to no log to console ... it's there for the initial getting started experience, but you don't need to send log messages to 2 places. On Tue, Oct 20, 2015 at 10:42 AM, Shawn Heisey wrote: > On 10/20/2015 9:19 AM, Eric Torti wrote: >>

Re: `cat /dev/null > solr-8983-console.log` frees host's memory

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