[
https://issues.apache.org/jira/browse/SOLR-6833?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14241596#comment-14241596
]
Alexandre Rafalovitch commented on SOLR-6833:
---------------------------------------------
bq. what about the cloud examples?
The cloud examples at the moment copy the whole server directory into node1 and
node2 in Solr root and then run from those. And re-running them requires
figuring out whatever command line the script used to start them and doing it
manually. There is no bin/start "previous cloud example"
I am quite unhappy about that, especially with the rest of the stuff discussed
above showing up in the server directory. I was told the latest code will
carefully avoid extra directories, but I am not totally sold.
Also, the node1/node2 is nearly invisible in the directory and will cause
confusion. I think they should be at least prefixed with the example name or
something.
> 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
>
>
> 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: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
