[
https://issues.apache.org/jira/browse/SOLR-6833?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14246007#comment-14246007
]
Alexandre Rafalovitch commented on SOLR-6833:
---------------------------------------------
Looks good. I hit a script bombing out on mis-spelt name, so opened a SOLR-6848
for that.
The rest here are just random thoughts from using the scripts, feel free to
ignore if this has already been discussed.
# The example run will generate console.log, even though log4j for example does
not send anything to it. So the file is always empty.
# There is also solr_gc.log for the examples, I am not sure if that's a big
deal. It grows kind of fast, but so does the main log.
# In the script, if the port is busy, is says:
{quote}
Port 8983 is already being used by another process (pid: 13221)
{quote}
Could be even more - first user - nicer to add after: _Use -p flag to start
with a different port_.
> bin/solr -e foo should not use server/solr as the SOLR_HOME
> -----------------------------------------------------------
>
> Key: SOLR-6833
> URL: https://issues.apache.org/jira/browse/SOLR-6833
> Project: Solr
> Issue Type: Bug
> Reporter: Hoss Man
> Assignee: Timothy Potter
> Fix For: 5.0
>
> Attachments: SOLR-6833.patch
>
>
> i think it's weird right now that running bin/solr with the "-e" (example)
> option causes it to create example solr instances inside the server directory.
> i think that's fine for running solr "normally" (ie: "start") but if you use
> "-e" that seems like the solr.solr.home for those example should instead be
> created under $SOLR_TIP/example.
> I would even go so far as to suggest that the *log* files created should live
> in that directory as well.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
