What about the Garbage Collection output? I think we have the same issue there. Frankly, I don't know how many people know what to do with that in a first place.
---- Solr Analyzers, Tokenizers, Filters, URPs and even a newsletter: http://www.solr-start.com/ On 6 November 2015 at 11:11, Upayavira <u...@odoko.co.uk> wrote: > Erick, > > bin/start pipes stdout to solr-$PORT-console.log or such. With no > rotation. So we are setting people up to fail right from the get-go. > > That's what I'm hoping the attached ticket will resolve. > > Upayavira > > On Fri, Nov 6, 2015, at 03:52 PM, Erick Erickson wrote: >> How do you start solr? If you pipe console output >> to a file it'll grow forever. Either pipe the >> output to dev/null or follow Sara's link and >> take the CONSOLE appender out of log4j.properties >> >> Best, >> Erick >> >> On Fri, Nov 6, 2015 at 2:12 AM, sara hajili <hajili.s...@gmail.com> >> wrote: >> > You can change solr loglevel.bydefault solr logs for every thing. >> > You can change this by go in solrconsole.inlog/level and edit levels for >> > just error for example. >> > And this is temporary way. >> > You can also change solrconfig.insolr_home >> > In /log and change logging4j >> > Config. >> > For more info look at: >> > https://cwiki.apache.org/confluence/display/solr/Configuring+Logging >> > That log file is constantly growing. And it is now ~60GB. what can i change >> > to fix this? >> > >> > >> > >> > -- >> > View this message in context: >> > http://lucene.472066.n3.nabble.com/solr-8983-console-log-is-huge-tp4238613.html >> > Sent from the Solr - User mailing list archive at Nabble.com.
