[ 
https://issues.apache.org/jira/browse/SOLR-11957?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16385894#comment-16385894
 ] 

ASF subversion and git services commented on SOLR-11957:
--------------------------------------------------------

Commit fc8c239f93da4deb2adc1a2953793377ae5f4a53 in lucene-solr's branch 
refs/heads/master from [~shalinmangar]
[ https://git-wip-us.apache.org/repos/asf?p=lucene-solr.git;h=fc8c239 ]

SOLR-11957: Increase MaxFileSize=32MB and MaxBackupIndex=10 for 
RollingFileAppender in log4j.properties


> Increase MaxFileSize for RollingFileAppender in log4j.properties
> ----------------------------------------------------------------
>
>                 Key: SOLR-11957
>                 URL: https://issues.apache.org/jira/browse/SOLR-11957
>             Project: Solr
>          Issue Type: Improvement
>      Security Level: Public(Default Security Level. Issues are Public) 
>          Components: logging
>            Reporter: Shalin Shekhar Mangar
>            Priority: Minor
>             Fix For: master (8.0), 7.3
>
>         Attachments: SOLR-11957.patch, SOLR-11957.patch
>
>
> The current MaxFileSize for RollingFileAppender is set to 4MB. This is too 
> low for most production deployments. Very frequently we handle support cases 
> for people where the logs have long since rolled over and finding out what 
> happened just an hour ago requires digging through old log files (if they 
> even exist because MaxBackupIndex=9).
> I propose the MaxFileSize be set to 64MB and MaxBackupIndex=5 to have max log 
> size bounded to 320MB.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org

Reply via email to