Is Quiesce always required to shutdown Pega
Hi,
Customer asks if Pega requires "Quiesce" operation every time a node is shutdown so Pega cleans up the mess. I know Pega takes a node out of a Hazelcast cluster gracefully if you quiesce, but this is for server maintenance purpose right? I believe we do not need to do this every time for every for regular startup / shutdown, but is that correct? shutdown.sh in Tomcat bin directory seems to delete a row in a pr_sys_statusnodes table and I assume this is still graceful shutdown, and no any mess should be left. Please help us to clarify our confusion.
Thanks,
Proximus
BE
Hello,
We never quiesce before a shutdown.
I think this is required if you want to isolate a node. After some time, no more users will be connected to this quiesced node.
With a full shutdown or after server crash/kill, PEGA manages pretty well to reconnect all nodes when back up & running.
We're running with websphere & oracle.
Regards
Anthony
Updated: 7 Sep 2020 5:15 EDT
IT Solution Service
SG
So I would take your answer as shutdown.sh is a formal process.
Then my question is, what exactly do people use Quiesce for? I just tried Quiesce but it did not shutdown Tomcat. Tomcat is still up and running, and it just doesn't accept any web requests. Well, if Quiesce is only for maintenance purpose, I would simply shutdown Tomcat so it is easier for me to do work (upgrade work, OS patch installation, etc). The node has to be taken out of load balancer distribution path prior to shutdown or quiesce anyways, so to me Quiesce is meaningless.
Can anyone give a good reason to use Quiesce over shutdown?
Thanks,