[
https://issues.apache.org/jira/browse/SOLR-10632?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16002719#comment-16002719
]
Jan Høydahl commented on SOLR-10632:
------------------------------------
It may be that we can try to think a bit harder whether it is possible to
detect if a running solr is using the same log directory.
Suggestion 1: Before moving files, list all .pid files, say you find
{{solr-8983.pid}}. Then look for a {{$SOLR_LOGS_DIR/solr-$PORT-console.log}}
file, do NOT rotate those logs, and either refuse to start or yell a big fat
warning in the logs of the new instance that you're using same log directory as
a running instance and give a hint about changing SOLR_LOGS_DIR?
> logfiles are moved to archived if server is still running
> ---------------------------------------------------------
>
> Key: SOLR-10632
> URL: https://issues.apache.org/jira/browse/SOLR-10632
> Project: Solr
> Issue Type: Bug
> Security Level: Public(Default Security Level. Issues are Public)
> Components: logging
> Affects Versions: 6.5
> Reporter: Bernd Fehling
> Priority: Minor
>
> There are server logfiles without portnumber in logfile name. If another
> instance is started these logfiles are moved to archived, eventhough the
> other server is still running.
> Solution could be to give every logfile a name with the portnumber it belongs
> to. Or check if a logfile is still in use and quit with an error before
> moving to archived.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
