[jira] [Commented] (SOLR-15104) Restart solr will override the gc log

["Christine Poerschke (Jira)" <ji...@apache.org>]

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

Christine Poerschke commented on SOLR-15104:
--------------------------------------------

The {{SOLR_LOG_PRESTART_ROTATION}} option was removed in SOLR-12144 to leverage log4j2 instead. The option included gc log archiving. I wonder if introduction of (say) a {{SOLR_GC_LOG_PRESTART_ARCHIVE}} option could solve the issue here – [https://github.com/apache/solr/pull/16] to illustrate.

Though {{solr_gc-%t.log}} style gc logs and/or archived gc logs might both require users to adjust their gc log housekeeping approaches?

> Restart solr will override the gc log
> -------------------------------------
>
>                 Key: SOLR-15104
>                 URL: https://issues.apache.org/jira/browse/SOLR-15104
>             Project: Solr
>          Issue Type: Improvement
>            Reporter: Hongxu Ma
>            Priority: Minor
>          Time Spent: 10m
>  Remaining Estimate: 0h
>
> When restarting Solr, it will override the previous java gc log.
> This behavior is not friendly for debugging OOM, looks it is caused by the hard-code gc param (in bin/solr):
> [https://github.com/apache/lucene-solr/blob/3e2fb59272f5b4d8106b3d8edf847f50bacd7a61/solr/bin/solr#L2031]
>  
> Refer other sys, I think add timestamp in default gc filename will be better.
> https://issues.apache.org/jira/browse/HBASE-18274
> https://issues.apache.org/jira/browse/CASSANDRA-2418
>  
> Hope it can be improved, thanks.
>  



--
This message was sent by Atlassian Jira
(v8.3.4#803005)