[
https://issues.apache.org/jira/browse/SOLR-7728?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14603663#comment-14603663
]
Shawn Heisey commented on SOLR-7728:
------------------------------------
That probably would have been obvious if I had looked at what happens with the
console log, but I didn't check that first.
Devils advocate note: Why do you want more than one Solr instance per machine?
One Solr instance can handle any number of indexes, and running multiple
instances will waste resources like memory, as well as make it necessary to be
aware of the port number instead of simply letting all Solr instances run on
the same port.
If you're running the cloud example, the different logs from each node are
already in separate directories.
> 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
>
> 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: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
