Hi Thanks for reporring. This definitely looks like a bug, would you be able to open a JIRA issue for tracking it?
Jan > 4. aug. 2026 kl. 16:36 skrev Mikael Sterner <[email protected]>: > > Hi! > > When using the Solr Control Script to start Solr 10.0.0 on Windows in User > Managed mode, it checks the status of all currently running Solr instances: > > solr-10.0.0-slim\bin\solr.cmd start --user-managed -p 8981 > Waiting up to 180 seconds to see Solr running on port 8981 > Started Solr server on port 8981. Happy searching! > > solr-10.0.0-slim\bin\solr.cmd start --user-managed -p 8982 > Waiting up to 180 seconds to see Solr running on port 8981 > Started Solr server on port 8981. Happy searching! > Waiting up to 180 seconds to see Solr running on port 8982 > Started Solr server on port 8982. Happy searching! > > > In Solr 9.10.1 it only waits for the specified Solr instance: > > solr-9.10.1-slim\bin\solr.cmd start -p 8981 > Waiting up to 180 seconds to see Solr running on port 8981 > Started Solr server on port 8981. Happy searching! > > solr-9.10.1-slim\bin\solr.cmd start -p 8982 > Waiting up to 180 seconds to see Solr running on port 8982 > Started Solr server on port 8982. Happy searching! > > > If this behavior is not intentional, it seems like a regression from > https://issues.apache.org/jira/browse/SOLR-17685, where the “simplified” > solr.cmd script no longer passes in --solr-url to the status tool: > https://github.com/apache/solr/pull/3223/changes#diff-118de7ae5d9fc032e479321cb4d3ee62ceb68e9f3c845292b44c5e14c0f769cfL1178 > (This makes it fall back to waiting for all Solr instances found in the PID > directory.) > > Yours, > Mikael Sterner
