[ https://issues.apache.org/jira/browse/SOLR-16981?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17765848#comment-17765848 ]
Jan Høydahl commented on SOLR-16981: ------------------------------------ So I tested solr stop -all again (with SOLR_PORT set). * It works as it should on main, even before the unintended merge. * It works in branch_9x as well. * It fails in 9.3. So that bug was fixed as a side effect of SOLR-16941. So for this JIRA's sake let's revert the wrong commit and close as Done. Wrt the 'solr stop' without options I believe current behavior is correct, but we could document it better. No need for a Jira for that I guess. > 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: 1h 40m > 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