Close popover
olivier K (olivierK7667)
Personal and Business Computers

Personal and Business Computers
olivierK7667 Member since 2017 2 posts
Personal and Business Computers
Posted: January 5, 2018
Last activity: February 20, 2018

Issue performance Deploying Pega Platform 7.3.1 on Microsoft Azure Cloud High availability

I built a high availability architecture on Microsoft Cloud Azure for using Pega platform 7.3.1 .

My architecture is as follows:

1 Azure Application Gateway => 2 Apache 2.4 Reverse Proxy Servers => 1 Azure Internal Loadbalancer => 2 Tomcat 7 Application Servers => 1 PostgreSql 9.6 Database Server ( I will use 2 servers for the futur : Master/Slave)

When the 2 tomcats servers are active, Pega team developers have some slowly or crashing while using the Pega prweb interface (tasks example : import project , Add a participants,quotation validation).

After several investigations, I noticed that by activating a single tomcat server, the navigation from the interface prweb pega is more fluid (more slowness, or chrash).

Note: I want to clarify that I do not have affinity session enabled at the Azure Internal Loadbalancer level because I only have 2 Affinity session options ( IP Client or Affinity session with Client Ip and Protocol )

However, in Pega's High Availability install documentation, it recommends configuring session affinity with cookie (which is not possible for Azure Internal Loadbalancer).

"Configuring affinity session
Affinity session is configured with the load balancer. It ensures that all requests from a user are handled
by the same Pega Platform server.
Production load balancers offer a range of options for configuring session affinity. Pega Platform supports
cookie-based affinity. Configure cookies for high availability session affinity using the following
Session / ha / quiesce / customSessionInvalidationMethod
Affinity session configuration is only applicable when using slow drain for quiesce.
l Value - configurable-cookie-invalidator or fully qualified class
SessionInvalidationMethod in prpublic
l Functionality - Class name of the invalidation method in use
Set to configurable-cookie-invalidator to perform cookie-based invalidation using the value
of session / ha / quiesce / cookieToInvalidate as the name of the cookie to invalidate
l Set up the interface of the interface
SessionInvalidationMethod in prpublic
Session / ha / quiesce / cookieToInvalidate
Affinity session configuration is only applicable when using slow drain for quiesce.
l Value - Name of the cookie to invalidate
Functionality - Name of the cookie to invalidate when using the configurable-cookie-invalidator
Tier architecture application
Highly available tier architectures must have enough computing power to support fail-over,
more servers for support.
To deploy a highly available production system, two or more virtual machines are needed.
These allow for horizontal cluster
offer a solution for crash recovery. Each machine can deploy one or more Pega Platform servers.
Organizations can employ vertical cluster by adding multiple Pega Platform server instances to
production load support. Determine the number of the Pega Platform server instances based on capacity
planning and by consideration operational thresholds.
For information on support for server platform versions, see the Support Platform Guide on the
NDS. "

I have therefore made the following hypothesis concerning the origin of problem encounter :

- Session management concerns at the Azure Internal loadbalancer

- Concerns about high availability management (Azure loadbalancer / Pega application on Tomcat application server side)

- Or elsewhere in the connection chain (architecture)

Thank you in advance for your help, URGENT!

System Administration
Moderation Team has archived post