You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@solr.apache.org by Reej Nayagam <re...@gmail.com> on 2022/02/17 08:05:29 UTC
Re: Solr Stop Port
Hi All,
I was able to set the stop port and everything was working fine.
Initial setup was to use SSL, now we need to turn off SSL and so we changed
all the configs in solr.in.cmd
when we stop the first instance in the server using the command solr stop
-p 3883, node 3883 goes down and 9883 is up and running - which is correct
Now the issue is when both the nodes are up and when we issue the stop
command to stop instance 2 (9883) , instance 1 also stops.
command used : solr stop -p 9883
stops both 3883 and 9883
I commented out the stop_port = 6400 in solr.in.cmd, and now it works
perfectly.
so Kindly advise if we need to configure the stop_port for each node or
is it a different issue, or is it a cache or something that is happening
bcoz of the earlier ssl setup.
I cleared all the zk data folders and solr nodes having the replicas and
did a fresh setup of the nodes
*Thanks,*
*Reej*
On Mon, Jan 10, 2022 at 3:36 PM Reej Nayagam <re...@gmail.com> wrote:
> Thanks Shawn, this worked.
> Thank you for the explanation & the help.
>
>
> *Thanks & Regards*
> *Reej*
>
>
> On Mon, Jan 10, 2022 at 7:45 AM Shawn Heisey <ap...@elyograg.org> wrote:
>
>> 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
>>
>
Re: Help required in Solr Stop Port - resolved
Posted by Reej Nayagam <re...@gmail.com>.
Hi All,
I managed to find the issue, since 2 instances are running in the same
server, both the instances were assigned the same stop_port that we have
defined in the solr.in.cmd file. while we were trying to bring one port
down, since the same stop_port was being shared by the other node too, both
came down. But not sure why we didn’t face this issue earlier, might be
because solr was shutdown properly and now, as solr was not shutdown
gracefully the jetty ports were used and that might have caused the issue.
Now based on the solr ports, manually assigned the stop_port in solr.cmd
file, and now different stop ports are assigned to the 2 different nodes.
*Thanks,*
*Reej*
On Fri, Feb 18, 2022 at 9:26 AM Reej Nayagam <re...@gmail.com> wrote:
> Hi All,
> We have Solr cloud setup, version : 8.8.2
>
> I was able to set the stop port and everything was working fine.
>
> Initial setup was to use SSL, now we need to turn off SSL and so we
> changed all the configs in solr.in.cmd
>
> when we stop the first instance in the server using the command solr stop
> -p 3883, node 3883 goes down and 9883 is up and running - which is correct
>
> Now the issue is when both the nodes are up and when we issue the stop
> command to stop instance 2 (9883) , instance 1 also stops.
>
> command used : solr stop -p 9883, stops both 3883 and 9883
>
> I commented out the stop_port = 6400 in solr.in.cmd, and now it works
> perfectly.
>
> so Kindly advise if we need to configure the stop_port for each node or
> is it a different issue, or is it a cache or something that is happening
> bcoz of the earlier ssl setup.
>
> I cleared all the zk data folders and solr nodes having the replicas and
> did a fresh setup of the nodes
>
>
> *Thanks,*
> *Reej*
>
>
> On Mon, Jan 10, 2022 at 3:36 PM Reej Nayagam <re...@gmail.com> wrote:
>
>> Thanks Shawn, this worked.
>> Thank you for the explanation & the help.
>>
>>
>> *Thanks & Regards*
>> *Reej*
>>
>>
>> On Mon, Jan 10, 2022 at 7:45 AM Shawn Heisey <ap...@elyograg.org> wrote:
>>
>>> 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
>>>
>>
Help required in Solr Stop Port
Posted by Reej Nayagam <re...@gmail.com>.
Hi All,
We have Solr cloud setup, version : 8.8.2
I was able to set the stop port and everything was working fine.
Initial setup was to use SSL, now we need to turn off SSL and so we changed
all the configs in solr.in.cmd
when we stop the first instance in the server using the command solr stop
-p 3883, node 3883 goes down and 9883 is up and running - which is correct
Now the issue is when both the nodes are up and when we issue the stop
command to stop instance 2 (9883) , instance 1 also stops.
command used : solr stop -p 9883, stops both 3883 and 9883
I commented out the stop_port = 6400 in solr.in.cmd, and now it works
perfectly.
so Kindly advise if we need to configure the stop_port for each node or
is it a different issue, or is it a cache or something that is happening
bcoz of the earlier ssl setup.
I cleared all the zk data folders and solr nodes having the replicas and
did a fresh setup of the nodes
*Thanks,*
*Reej*
On Mon, Jan 10, 2022 at 3:36 PM Reej Nayagam <re...@gmail.com> wrote:
> Thanks Shawn, this worked.
> Thank you for the explanation & the help.
>
>
> *Thanks & Regards*
> *Reej*
>
>
> On Mon, Jan 10, 2022 at 7:45 AM Shawn Heisey <ap...@elyograg.org> wrote:
>
>> 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
>>
>