[
https://issues.apache.org/jira/browse/SOLR-6962?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17885575#comment-17885575
]
ASF subversion and git services commented on SOLR-6962:
-------------------------------------------------------
Commit 34f77886104a15f9e478cf7b4a5f6b0691d79eb7 in solr's branch
refs/heads/main from Eric Pugh
[ https://gitbox.apache.org/repos/asf?p=solr.git;h=34f77886104 ]
SOLR-6962: bin/solr stop/start/restart should complain about missing value for
options that expect a value. (#2671)
We parse the args for the start/stop/restart commands separate from actually
invoking the command.
This means you don't get an error message for passing a start arg, like
--jvm-opts to a stop commmand, which can cause a hang in running these
commands. This prevents the hang and provides a message.
> bin/solr stop/start/restart should complain about missing value for options
> that expect a value.
> ------------------------------------------------------------------------------------------------
>
> Key: SOLR-6962
> URL: https://issues.apache.org/jira/browse/SOLR-6962
> Project: Solr
> Issue Type: Improvement
> Components: scripts and tools
> Affects Versions: 5.0
> Reporter: Alexandre Rafalovitch
> Assignee: Eric Pugh
> Priority: Minor
> Labels: pull-request-available
> Attachments: SOLR-6962.patch, SOLR-6962v2.patch
>
> Time Spent: 1h 50m
> Remaining Estimate: 0h
>
> *bin/solr* has a *-a* option that expects a second parameter. If one is not
> provided, it hangs. It should complain and exit just like *-e* option does.
> The most common time I hit this is when I try to do *bin/solr stop \-all* and
> instead just type *bin/solr stop \-a* as I am more used to give full name
> options with double-dash prefix (Unix conventions, I guess).
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
