You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by "Jan Høydahl (JIRA)" <ji...@apache.org> on 2016/10/24 12:37:58 UTC

[jira] [Resolved] (SOLR-7506) Roll over GC logs by default via bin/solr scripts

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

Jan Høydahl resolved SOLR-7506.
-------------------------------
    Resolution: Fixed

This is now in. An improvement could be to keep the logs in {{archive/}} for a few days instead of deleting on every startup...

> 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, 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-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org