On 11/27/2018 7:29 AM, Gus Heck wrote:
Startup logging that happens just on startup should err on the side of
verbosity.
I think this is a good policy.
As I said before, I really do applaud the efforts to shrink the logs and
eliminate cruft. But I don't think that the motivation and goal should
just be "short logs". It should be about ensuring that the only thing
being logged by default is information that most users will find to be
relevant, and moving other logs to less severe logging levels.
The default logging should provide information that helps out in
something I like to think of as "typical troubleshooting". Startup and
reload logging can be a fairly verbose. Unless the user is doing
something very odd, that information is not likely to be logged frequently.
In some cases, achieving the goal I've outlined might mean *ADDING* some
logging to the default level, to provide information about unexpected
situations.
The logging that typically happens during normal operation (queries and
updates, mostly) only really gets verbose if the server is busy. I
don't know that there's much cruft in that logging, but we can review it
just to make sure. Giving the user the option to push request logging
into a separate logfile would do a lot to reduce the size of the main
log. Troubleshooting is sometimes more difficult when logs are
separated, but if that becomes an issue the user can always reconfigure
to put it all back in solr.log.
Thanks,
Shawn
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
