[
https://issues.apache.org/jira/browse/SOLR-7506?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15585294#comment-15585294
]
Jan Høydahl commented on SOLR-7506:
-----------------------------------
We don't necessarily need the timestamp in the file name, since we'll anyway
move logs away into {{archived/}} on every start, and delete the previous
generation every time. An alternative to moving gc files to {{archived/}}
(SOLR-9570) could however be to leave them in SOLR_LOGS_DIR *with* timestamp in
filename, and then on every restart a new set of rotated gc logs will be
created, and then we delete solr_gc_* files >7days old on 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
>
>
> 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: [email protected]
For additional commands, e-mail: [email protected]
