[
https://issues.apache.org/jira/browse/SOLR-7728?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15621960#comment-15621960
]
Jan Høydahl commented on SOLR-7728:
-----------------------------------
I think we should close this as won't fix and recommend that a user starting
multiple nodes from the same server directory uses different SOLR_LOGS_DIR
variables for each. Else, you'll have the same problem also with solr.log. Note
that the variable supports relative dir, so to achieve logging to e.g.
{{solr/server/8983-logs}} you could issue:
{noformat}
SOLR_LOGS_DIR=8983-logs ; bin/solr -p 8983
SOLR_LOGS_DIR=8080-logs ; bin/solr -p 8080
{noformat}
PS: We recently added GC log rotation, so the gc logs will be named
{{solr_gc.log.\{0-9\}\[.current\]}}
> bin/solr script: add port number to GC log filename
> ---------------------------------------------------
>
> Key: SOLR-7728
> URL: https://issues.apache.org/jira/browse/SOLR-7728
> Project: Solr
> Issue Type: Improvement
> Components: scripts and tools
> Affects Versions: 5.2.1
> Reporter: Crawdaddy
> Assignee: Gregory Chanan
> Attachments: SOLR-7728-Branch5X.patch, SOLR-7728.patch,
> SOLR-7728.patch
>
>
> It'd be nice if the bin/solr script added the node's port number to the GC
> log file name in the same way it does for the console log.
> This helps those of us who run multiple nodes per machine match node <-> log.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
