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
On Tue, Jan 3, 2017 at 5:10 PM, Shawn Heisey <apa...@elyograg.org> wrote: > On 1/3/2017 1:12 PM, Webster Homer wrote: > > We use the default log4j.properties file which rolls the log file to > > solr.log.1, solr.log.2 ... which isn't really the problem. What is > > also happening is that solr.log.1 gets renamed to > > solr_log_20170103_1110 with a timestamp as the file name. How do I > > turn off this behavior? It is not obvious in the log4j.properties file. > > That rename is not done by log4j. It is done by the bin/solr or > bin\solr.cmd script just before Solr is started. Unlike the solr.log.N > files, those files are not subject to automatic deletion. > > My best guess is that you've got a situation where something external to > Solr is restarting Solr frequently. Solr's start script renames > solr.log to solr_log_DATE_TIME each time it starts. As far as I am > aware, Solr does NOT have the ability to restart itself, and the CDCR > page in the reference guide doesn't mention anything about processes > being restarted as part of its operation. > > Because the logfiles that you are seeing accumulate are not handled by > log4j, switching to log4j2 and adding compression will not help. Moving > to log4j2 requires a few things to be done on the development side, and > won't be trivial. > > If your system requires frequent Solr restarts for some reason, then > you're going to have to take over management of the renamed solr > logfiles as well, or edit the start script so that it doesn't rename the > main logfile. SolrCloud does not deal well with frequent restarts, so > avoid doing them. > > Thanks, > Shawn > > -- This message and any attachment are confidential and may be privileged or otherwise protected from disclosure. If you are not the intended recipient, you must not copy this message or attachment or disclose the contents to any other person. If you have received this transmission in error, please notify the sender immediately and delete the message and any attachment from your system. Merck KGaA, Darmstadt, Germany and any of its subsidiaries do not accept liability for any omissions or errors in this message which may arise as a result of E-Mail-transmission or for damages resulting from any unauthorized changes of the content of this message and any attachment thereto. Merck KGaA, Darmstadt, Germany and any of its subsidiaries do not guarantee that this message is free of viruses and does not accept liability for any damages caused by any virus transmitted therewith. Click http://www.emdgroup.com/disclaimer to access the German, French, Spanish and Portuguese versions of this disclaimer.
