> bq. I don't want to see file limit warnings on a dev laptop > > "If you no longer wish to see this warning, set SOLR_ULIMIT_CHECKS to > false in your profile or solr.in.sh" > > Not having these limits set properly has caused weird errors for a lot > of people, but I agree they are annoying at times so there's a way to > shut them off.
Note my wording - "on a dev laptop". We can find a way to distinguish between dev/prod usage and only warn about file descriptors, suspiciously low heap, lack of SSL etc if Solr is bound to a public IP address. > The only logging config files you should have to worry about are in > ./solr/server/resources..... > > But yeah, there are several Solr JIRAs lying around that I'll break > some time loose _sometime_ to work on to try to make logging more > rational. Unfortunately as Shawn says, there's always tension. When > running "normally", I pretty much only want to see WARN messages. Then > every time I want to diagnose something, I want to see _everything_. > And telling the user to change their logging and call me again next > time the problem happens is not very satisfying for anyone. It is super easy to change the log level of one particular class or package selectively, that's why we have log4j2.xml and also the Admin's Logging levels menu. The occational need to see all of the 150 jar files loaded on startup should not be solved by spewing out that for first-time users of Solr who really just care for whether the server started OK or not. Agree that adding commented-out snippets in the logging config could be a good way to quickly let people debug "ClassNotFound issues", "Indexing issues", "Faceting issues", "Security issues" etc. We could have pre-canned configs that would upper the logging of classes of particular interest for each case. Jan
