Question
Ernst & Young
IN
Last activity: 16 Feb 2021 5:54 EST
AWS Auto scalng policy impacts on pega
Pega is hosted on AWS cloud and we have enabled autoscaling policy for our multi node environment . We use AMI to launch server based on server need.
We will be doing both horizontal and vertical scaling on EC2 servers, which means our server might get terminated and new servers would be launched based on AMI script that we have defined.
Q1: What will happen to my clipboard data when server get terminated and new one launched?
Q2: Like Q1, what are all the points i should think while we opt for auto sclaing policy ? (eg . stateless server- does not stores data on server)
I have gone through below link but did not found answer to my questions. Please help in answering these questions pls. Thanks in Advance !!
Cognitonic Systems Australia
AU
Hi @Ponnurangam ,
When ever any node is terminated data that is present in the Clipboard till that moment is not stored any where in Pega tables. When ever a node is terminated and new node is spinned-off user should re-login again to the Portal if it is single node environment.
Consider a process like any Queue Processor is processing the item and in the middle of the process node in which QP running violated the AWS policy, then that node will be terminated and the process will be stopped until the node is spinned-off. Once new node is formed the process starts again from stating onwards.