[
https://issues.apache.org/jira/browse/SOLR-11902?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16339636#comment-16339636
]
Shawn Heisey commented on SOLR-11902:
-------------------------------------
[~erickerickson] commented this in an email reply:
bq. Makes sense, I suspect that create_core will happily create a core on a
different node, but can't check now...
In what I would call typical situations, this won't work, because
${instanceDir}/conf must exist and be populated before the CoreAdmin call,
which bin/solr can't do on a remote host. If using configsets (which I
wouldn't call typical), then it would work.
> bin/solr help text should mention when commands must be run from Solr host
> --------------------------------------------------------------------------
>
> Key: SOLR-11902
> URL: https://issues.apache.org/jira/browse/SOLR-11902
> Project: Solr
> Issue Type: Improvement
> Security Level: Public(Default Security Level. Issues are Public)
> Components: documentation, scripts and tools
> Affects Versions: master (8.0)
> Reporter: Jason Gerlowski
> Priority: Minor
> Labels: documentation
>
> The {{bin/solr}} scripts contain a number of useful tools. Some of these can
> be pointed at a Solr host through config, and can be run on the Solr host, an
> admin's laptop, or anywhere else. Others make assumptions that require them
> to be run from the same box where Solr is running.
> These commands should document any such restrictions in their help text, to
> avoid any potential confusion.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
