[jira] [Commented] (SOLR-11902) bin/solr help text should mention when commands must be run from Solr host
[
https://issues.apache.org/jira/browse/SOLR-11902?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16359084#comment-16359084
]
ASF subversion and git services commented on SOLR-11902:
Commit 09de0da79b09591f967d99648ef229c84a68d836 in lucene-solr's branch
refs/heads/branch_7x from [~gerlowskija]
[ https://git-wip-us.apache.org/repos/asf?p=lucene-solr.git;h=09de0da ]
SOLR-11902: Clarify bin/solr -h text to describe which commands can be run
remotely
The bin/solr scripts contain a number of independent tools. Many of
these can be run anywhere and just pointed at the correct Solr or ZK
host. Some must run on the machine hosting Solr itself.
This commit clarifies help text for each bin/solr command, indicating
whether it can be run remotely, or must be run locally.
> 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
>Assignee: Jason Gerlowski
>Priority: Minor
> Labels: documentation, patch
> Attachments: SOLR-11902.patch, SOLR-11902.patch
>
>
> 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
[jira] [Commented] (SOLR-11902) bin/solr help text should mention when commands must be run from Solr host
[
https://issues.apache.org/jira/browse/SOLR-11902?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16359081#comment-16359081
]
ASF subversion and git services commented on SOLR-11902:
Commit 11a23a90292d9eec39af6b61984e11ac6bb169b2 in lucene-solr's branch
refs/heads/master from [~gerlowskija]
[ https://git-wip-us.apache.org/repos/asf?p=lucene-solr.git;h=11a23a9 ]
SOLR-11902: Clarify bin/solr -h text to describe which commands can be run
remotely
The bin/solr scripts contain a number of independent tools. Many of
these can be run anywhere and just pointed at the correct Solr or ZK
host. Some must run on the machine hosting Solr itself.
This commit clarifies help text for each bin/solr command, indicating
whether it can be run remotely, or must be run locally.
> 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
>Assignee: Jason Gerlowski
>Priority: Minor
> Labels: documentation, patch
> Attachments: SOLR-11902.patch, SOLR-11902.patch
>
>
> 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
[jira] [Commented] (SOLR-11902) bin/solr help text should mention when commands must be run from Solr host
[
https://issues.apache.org/jira/browse/SOLR-11902?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16358517#comment-16358517
]
Jason Gerlowski commented on SOLR-11902:
I'm planning on committing this later today or this weekend, unless there are
any objections. Thought it would make a good trial "first commit". Will
upload a very very slightly revised patch in a few minutes.
> 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
>Assignee: Jason Gerlowski
>Priority: Minor
> Labels: documentation, patch
> Attachments: SOLR-11902.patch
>
>
> 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
[jira] [Commented] (SOLR-11902) bin/solr help text should mention when commands must be run from Solr host
[
https://issues.apache.org/jira/browse/SOLR-11902?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16341083#comment-16341083
]
Jason Gerlowski commented on SOLR-11902:
Thanks for the help guys. I verified the behavior that Shawn laid out above.
I've attached a patch with some modifications to the help text for the various
bin/solr commands. I wasn't able to take things as far as I initially thought;
some of the bin/solr commands are missing help text altogether, and others
(such as {{assert}}) have their help text generated from the {{commons-cli}}
library parsing the {{Options}} over in SolrCLI.java.
I'm happy to add the missing help text for those commands that need it. I'm
also happy to tweak the SolrCLI-generated help text to look more like that
output by the scripts. But I wasn't sure whether to tack on that work here, or
have them as separate JIRAs.
Don't have a strong preference personally, but didn't want to assume. Might
help this doc change to get in quicker if those slightly-related issues are
handled elsewhere. OTOH it might be easier to review them together. Unless I
hear otherwise, I'll split them off into different JIRA's I guess.
> 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
> Attachments: SOLR-11902.patch
>
>
> 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
[jira] [Commented] (SOLR-11902) bin/solr help text should mention when commands must be run from Solr host
[
https://issues.apache.org/jira/browse/SOLR-11902?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=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
[jira] [Commented] (SOLR-11902) bin/solr help text should mention when commands must be run from Solr host
[
https://issues.apache.org/jira/browse/SOLR-11902?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=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
