[
https://issues.apache.org/jira/browse/SOLR-11902?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16338626#comment-16338626
]
Jason Gerlowski commented on SOLR-11902:
----------------------------------------
The following {{bin/solr}} commands can only ever be run (or only make sense to
run) on the host on which Solr is running:
- start
- stop
- restart
- status
- version
- auth
- assert
- create_core (still need to test this)
These remaining {{bin/solr}} commands can be run on any host, as long as it can
talk to a remote Solr/ZK as needed:
- healthcheck
- create_collection
- delete
- zk
- assert
(Note that "assert" appears in both lists, as many of its options only make
sense when run locally, but some are valid in either context.)
> 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
