On 1/7/2022 4:55 AM, Reej Nayagam wrote:
I wonder how the existing port (8983) which is already being assigned to
solr4 is assigned to jetty stop.
Kindly let me know if we need to change the ports for jetty, I saw there
are 3 jetty xml with the default ports as 3983 inside solr\server\etc
folder
The startup script defaults to assigning the STOP port to 1000 lower
than the main Solr port. So if the Solr port is 8983, the stop port
will be 7983.
Though if you have changed Solr's port by editing jetty config files
directly instead of using environment variables via the include script
as was intended, maybe the chosen stop port has nothing to do with what
jetty is using for the Solr port.
Assuming a non-windows system, you can add "STOP_PORT=nnnn" to the
active solr.in.sh file to override this default and use what you want
for the stop port. The same thing can be done on Windows by editing
solr.in.cmd.
The stop port listens on localhost only. It cannot normally be used to
remotely stop Solr, even if the stop key is known. We have always
recommended that a Solr server should be installed in a network location
where unauthorized persons and systems cannot connect to it.
The startup script uses the stop port to gracefully stop Solr, and will
forcefully terminate the process if it does not stop gracefully.
For Solr 4.x, we did not have a startup script. I have no way of
knowing how things are set up on your 4.x system.
Thanks,
Shawn
