[
https://issues.apache.org/jira/browse/SOLR-16981?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17765564#comment-17765564
]
Jan Høydahl commented on SOLR-16981:
------------------------------------
So the PR was merged in error. We need to decide whether the "solr stop"
command with no args should have different behavior depending on whether
SOLR_PORT is set. I think I changed my mind and think the current 9.3 behavior
is OK. So perhaps revert?
That leaves two other issues from the description:
* the {{solr stop -all}} command will only try to stop solr on port 8983 if
the {{SOLR_PORT}} environment variable is set to 8983 --> Will try to reproduce
this and confirm
* However, the {{solr stop -all}} script will only consult pid files -->
[~houston] suggests it should only consult PS, not PID ? This should probably
be a separate JIRA
> bin/solr stop -all does not always find running processes
> ---------------------------------------------------------
>
> Key: SOLR-16981
> URL: https://issues.apache.org/jira/browse/SOLR-16981
> Project: Solr
> Issue Type: Bug
> Security Level: Public(Default Security Level. Issues are Public)
> Components: scripts and tools
> Reporter: Jan Høydahl
> Priority: Major
> Time Spent: 1.5h
> Remaining Estimate: 0h
>
> Spinoff from SOLR-16979.
> The {{solr status}} command checks SOLR_PID_DIR first, if nothing found it
> runs a {{ps}} command or something to find more. However, the {{solr stop
> -all}} script will only consult pid files, and give up if not found.
> Furthermore, the {{solr stop -all}} command will only try to stop solr on
> port 8983 if the {{SOLR_PORT}} environment variable is set to 8983. This is a
> bug.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@solr.apache.org
For additional commands, e-mail: issues-h...@solr.apache.org
