we use Pega as a single cluster on multi AZ in Openshift.
A database of Pega is active-standby with mirroring and, Pega accesses to a Virtual IP.
A user accesses to web(Pega) via load balancer.
in these environment,
1, How does a user manage a session?
2, How does Pega manage a session between databases?
3, if system failure with going down a container, what will be happened after changing active-standby of database?
@NagaakiA16892568
- User sessions in Pega are managed through session-based affinity support. This ensures that requests from one user are directed to a specific application server that maintains the state for that user. It is a Pega best practice to use cookie-based session affinity.
- Pega does not manage sessions between databases. Instead, it makes requests to a database. In a high availability setup, Pega supports database vendor-specific features and products for redundancy/failover at the database tier.
- In the event of a system failure that results in a container going down, Pega’s high availability features, combined with platform vendor solutions for database mirroring/DR and application server clustering, provide a comprehensive solution. If a node in the cluster crashes, Pega provides automated recovery support. The Pega platform is designed to store locally any in-process work, which allows the user to resume processing from the stopping point after a system interruption or failure.
This is a GenAI-powered tool. All generated answers require validation against the provided references.
Setting up load balancers
Pega Cloud High Availability > Putting it all Together
Pega Logical Architecture
Multi-datacenter setup in 8.6.1 with two Openshift clusters
Alignment to GDS’s Technology Code of Practice