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 <thelabd...@gmail.com> wrote: > 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 <apa...@elyograg.org> 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 >> -- Regards, Shalin Shekhar Mangar.
