On 1/6/2017 8:21 AM, Webster Homer wrote: > I figured our problem with the filesystem, by default the root logger > is configured with the CONSOLE logger, which is NOT rotated and > eventually filled up the file system. That doesn't exonerate the CDCR > logging problem though. The thing writes a huge amount of junk to the > logs, information that looks more like Debug and even TRACE level > statements. I hope that this is addressed, and soon! There doesn't > seem to be a way to turn it off either. We want INFO level logging
The logging that goes to the console and solr.log by default is INFO. Even without CDCR, INFO logging is fairly verbose, but normally doesn't chew up a whole bunch of gigabytes over a short timeframe. CDCR is a pretty new feature, and the authors likely needed a lot of information in the logs while they were developing it so they could chase down bugs. I have never used the feature and haven't looked at the logging, but it sounds like much of it could be changed to DEBUG or lower priority now that primary development is done. If you haven't already opened an issue in Jira to reduce what CDCR logs at INFO, that would be a good idea. To get rid of the console logging entirely, which is a good idea, edit server/resources/log4j.properties. Change the "log4j.rootLogger" line to remove CONSOLE and the comma. Optionally, you can also remove all the other lines that contain CONSOLE. Starting in version 6.3, you can put "-Dsolr.log.muteconsole" on the java commandline (normally you'd do this in the solr.in.* script) to accomplish this without changing the logging config. I personally think that Solr shouldn't log to the console at all unless it is running in the foreground and the console isn't being redirected to a file. https://issues.apache.org/jira/browse/SOLR-8186 Thanks, Shawn
