[ 
https://issues.apache.org/jira/browse/SOLR-7506?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jan Høydahl updated SOLR-7506:
------------------------------
    Attachment: SOLR-7506.patch

Patch
* Enables rotation of GC logs per suggestion of Shalin. Keeps 9 generations, 
20M each
* Names the gc log {{solr_gc_YYYYmmddHHMMss.log}}, which will be suffixed with 
{{.N\[.current\]}} by the JRE

NOTE: This should be applied on top of SOLR-9570, else we're creating a new 
problem with ever-increasing logs

> Roll over GC logs by default via bin/solr scripts
> -------------------------------------------------
>
>                 Key: SOLR-7506
>                 URL: https://issues.apache.org/jira/browse/SOLR-7506
>             Project: Solr
>          Issue Type: Improvement
>          Components: scripts and tools
>            Reporter: Shalin Shekhar Mangar
>            Assignee: Jan Høydahl
>            Priority: Minor
>              Labels: logging
>             Fix For: 6.3, master (7.0)
>
>         Attachments: SOLR-7506.patch
>
>
> The Oracle JDK supports rolling over GC logs. I propose to add the following 
> to the solr.in.{sh,cmd} scripts to enable it by default:
> {code}
> -XX:+UseGCLogFileRotation -XX:NumberOfGCLogFiles=5 -XX:GCLogFileSize=20M
> {code}
> Unfortunately, the JDK doesn't have any option to append to existing log 
> instead of overwriting so the latest log is overwritten. Maybe we can have 
> the bin/solr script roll that after the process is killed?



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

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

Reply via email to