Question

10
Replies
1142
Views
AttilaB3 Member since 2017 2 posts
Saltech Consulting
Posted: 2 years ago
Last activity: 2 years 8 months ago
Closed

Pega 7.3.1 High Availability issue

Hi All,

I would like to ask for your help regarding Pega High Availability. I'm trying to configure a multi-node Pega 7.3.1 system with High Availability following the Pega 7.3.1 High Availability Administration Guide. The quiesce scenario test is failing as passivated sessions are not restored in the surviving node.

Environment:
I have two Jboss 6.4 EAP instances on my localhost and a shared PostgreSQL database. I'm using Pega 7.3.1 with WAR deployment and OS is Ubuntu 16.04.

After I start both of the application servers then based on the logs Hazelcast cluster seems ok:

server1's log
13:31:25,007 INFO [stdout] (Log4j2-AsyncLoggerConfig-1) 2017-11-23 13:31:25,007 [21c6282be11c.event-2] [ ] [ ] [ ] (til.HazelcastMembershipManager) INFO - New member joined cluster: Member: [name=SERVER@localhost:5702, address=mycomputer/127.0.0.1:5702, uuid=9a4eee28-5570-4014-8d32-76bf97edc9cb, mode=SERVER]
13:31:25,007 INFO [stdout] (Log4j2-AsyncLoggerConfig-1) 2017-11-23 13:31:25,007 [21c6282be11c.event-2] [ ] [ ] [ ] (.util.ClusterMembershipManager) INFO - Members [2] {
13:31:25,007 INFO [stdout] (Log4j2-AsyncLoggerConfig-1) 2017-11-23 13:31:25,007 [21c6282be11c.event-2] [ ] [ ] [ ] (.util.ClusterMembershipManager) INFO - Member: [name=f9448d8fca317ede15b128a19c691e4c, address=mycomputer/127.0.0.1:5701, uuid=c2c9fcb3-de47-49d1-a8e7-acc9b08ac43c, mode=SERVER] <== THIS node
13:31:25,007 INFO [stdout] (Log4j2-AsyncLoggerConfig-1) 2017-11-23 13:31:25,007 [21c6282be11c.event-2] [ ] [ ] [ ] (.util.ClusterMembershipManager) INFO - Member: [name=SERVER@localhost:5702, address=mycomputer/192.168.0.105:5702, uuid=9a4eee28-5570-4014-8d32-76bf97edc9cb, mode=SERVER] <== NEW node
13:31:25,008 INFO [stdout] (Log4j2-AsyncLoggerConfig-1) 2017-11-23 13:31:25,007 [21c6282be11c.event-2] [ ] [ ] [ ] (.util.ClusterMembershipManager) INFO - }
13:31:27,890 INFO [stdout] (Log4j2-AsyncLoggerConfig-1) 2017-11-23 13:31:27,890 [21c6282be11c.event-1] [ ] [ ] [ ] (l.MemberAliasIMapEntryListener) INFO - Updated member detail(s)
13:31:27,890 INFO [stdout] (Log4j2-AsyncLoggerConfig-1) 2017-11-23 13:31:27,890 [21c6282be11c.event-1] [ ] [ ] [ ] (l.MemberAliasIMapEntryListener) INFO - Old identifier = Member: [name=SERVER@localhost:5702, address=mycomputer/192.168.0.105:5702, uuid=9a4eee28-5570-4014-8d32-76bf97edc9cb, mode=SERVER]
13:31:27,890 INFO [stdout] (Log4j2-AsyncLoggerConfig-1) 2017-11-23 13:31:27,890 [21c6282be11c.event-1] [ ] [ ] [ ] (l.MemberAliasIMapEntryListener) INFO - New identifier = Member: [name=292f5f2b55a80e13dd6448b62035cedf, address=mycomputer/127.0.0.1:5702, uuid=9a4eee28-5570-4014-8d32-76bf97edc9cb, mode=SERVER]

server2's log:
13:31:16,398 INFO [stdout] (Log4j2-AsyncLoggerConfig-1) 2017-11-23 13:31:16,398 [ mycomputer] [ STANDARD] [ ] [ ] (uster.internal.ClusterProvider) INFO - Initializating Cluster Provider: HazelcastClusterProvider
13:31:16,399 INFO [stdout] (Log4j2-AsyncLoggerConfig-1) 2017-11-23 13:31:16,399 [ mycomputer] [ STANDARD] [ ] [ ] (.internal.ClusterConfiguration) INFO - Cluster Name: c4bddd8fd7f1aaaca5d021c6282be11c
13:31:16,399 INFO [stdout] (Log4j2-AsyncLoggerConfig-1) 2017-11-23 13:31:16,399 [ mycomputer] [ STANDARD] [ ] [ ] (.internal.ClusterConfiguration) INFO - Cluster Identifier: Default
13:31:16,400 INFO [stdout] (Log4j2-AsyncLoggerConfig-1) 2017-11-23 13:31:16,399 [ mycomputer] [ STANDARD] [ ] [ ] (.internal.ClusterConfiguration) INFO - Cluster Procotol: HAZELCAST
13:31:16,400 INFO [stdout] (Log4j2-AsyncLoggerConfig-1) 2017-11-23 13:31:16,399 [ mycomputer] [ STANDARD] [ ] [ ] (.internal.ClusterConfiguration) INFO - Transport Protocol: cluster
13:31:16,400 INFO [stdout] (Log4j2-AsyncLoggerConfig-1) 2017-11-23 13:31:16,399 [ mycomputer] [ STANDARD] [ ] [ ] (.internal.ClusterConfiguration) INFO - Port Range: 5701-5800
13:31:16,401 INFO [stdout] (Log4j2-AsyncLoggerConfig-1) 2017-11-23 13:31:16,399 [ mycomputer] [ STANDARD] [ ] [ ] (.internal.ClusterConfiguration) INFO - Encryption Enabled: false
13:31:16,401 INFO [stdout] (Log4j2-AsyncLoggerConfig-1) 2017-11-23 13:31:16,399 [ mycomputer] [ STANDARD] [ ] [ ] (.internal.ClusterConfiguration) INFO - Public Address: Not specified
13:31:16,401 INFO [stdout] (Log4j2-AsyncLoggerConfig-1) 2017-11-23 13:31:16,399 [ mycomputer] [ STANDARD] [ ] [ ] (.internal.ClusterConfiguration) INFO - Discovery Timeout: 10 MINUTES
13:31:16,401 INFO [stdout] (Log4j2-AsyncLoggerConfig-1) 2017-11-23 13:31:16,399 [ mycomputer] [ STANDARD] [ ] [ ] (.internal.ClusterConfiguration) INFO - # Discoverable Nodes: 2
13:31:27,058 INFO [stdout] (Log4j2-AsyncLoggerConfig-1) 2017-11-23 13:31:27,057 [ mycomputer] [ STANDARD] [ ] [ ] (til.HazelcastMembershipManager) INFO - New member joined cluster: Member: [name=SERVER@localhost:5702, address=mycomputer/127.0.0.1:5702, uuid=9a4eee28-5570-4014-8d32-76bf97edc9cb, mode=SERVER]
13:31:27,061 INFO [stdout] (Log4j2-AsyncLoggerConfig-1) 2017-11-23 13:31:27,061 [ mycomputer] [ STANDARD] [ ] [ ] (.util.ClusterMembershipManager) INFO - Members [2] {
13:31:27,061 INFO [stdout] (Log4j2-AsyncLoggerConfig-1) 2017-11-23 13:31:27,061 [ mycomputer] [ STANDARD] [ ] [ ] (.util.ClusterMembershipManager) INFO - Member: [name=f9448d8fca317ede15b128a19c691e4c, address=mycomputer/127.0.0.1:5701, uuid=c2c9fcb3-de47-49d1-a8e7-acc9b08ac43c, mode=SERVER]
13:31:27,062 INFO [stdout] (Log4j2-AsyncLoggerConfig-1) 2017-11-23 13:31:27,061 [ mycomputer] [ STANDARD] [ ] [ ] (.util.ClusterMembershipManager) INFO - Member: [name=SERVER@localhost:5702, address=mycomputer/127.0.0.1:5702, uuid=9a4eee28-5570-4014-8d32-76bf97edc9cb, mode=SERVER] <== THIS node <== NEW node
13:31:27,062 INFO [stdout] (Log4j2-AsyncLoggerConfig-1) 2017-11-23 13:31:27,061 [ mycomputer] [ STANDARD] [ ] [ ] (.util.ClusterMembershipManager) INFO - }
13:31:27,062 INFO [stdout] (Log4j2-AsyncLoggerConfig-1) 2017-11-23 13:31:27,062 [ mycomputer] [ STANDARD] [ ] [ ] (uster.internal.ClusterProvider) INFO - Successfully joined cluster _hzInstance_1_c4bddd8fd7f1aaaca5d021c6282be11c as Member: [name=SERVER@localhost:5702, address=mycomputer/127.0.0.1:5702, uuid=9a4eee28-5570-4014-8d32-76bf97edc9cb, mode=SERVER].
13:31:27,081 INFO [stdout] (Log4j2-AsyncLoggerConfig-1) 2017-11-23 13:31:27,080 [ mycomputer] [ STANDARD] [ ] [ ] (internal.PRClusterProviderImpl) INFO - Using system pulse type: cluster

In Pega Designer Studio I also can see cluster members.

Regarding my test scenario I logged into server1 with Portaluser@pega.com operator and created a new GeneralTask case. After that I initiated "Quiesce" on server1.
New messages in the log of server1:
14:16:07,027 INFO [stdout] (Log4j2-AsyncLoggerConfig-1) 2017-11-23 14:16:07,026 [http-/0.0.0.0:8180-5] [ STANDARD] [ ] [ ] ( pega.highavailability.quiesce) INFO - [BeginQuiesce] This node has started the quiesce process. Mode: immediateDrain
14:16:22,447 INFO [stdout] (Log4j2-AsyncLoggerConfig-1) 2017-11-23 14:16:22,446 [ Thread-326] [ ] [ ] [ ] ( pega.highavailability.quiesce) INFO - Node has entered state Quiesce Complete

In server2's log there were no any messages.

At this moment I didn't see portaluser@pega.com's session on the requestors tab in Designer Studio.

After that I changed the routing and routed portaluser's requests from server1 to server2. I got the login screen of server2 after I hit the submit button in user portal. There is no SSO configured. (Note: As far as I understood from HA administration guide SSO is not a must. It provides seamless user experience but my HA configuration should work without SSO as well.) So I had to do login with Portaluser but after login I didn't see the previously opened case. Even if I tried to open the given work object then I got a warning message regarding the missing lock.

On the requestors tab I saw a new Portaluser@pega.com session with new requestorID:

Could you please help me out? What did I miss?
How could I debug my configuration?

Thank you in advance,
Attila

***Updated by moderator: Lochan to mask proprietary information***

***2/2/18: Updated by moderator: Lochan to close post***

Low-Code App Development Installation and Deployment
Moderation Team has archived post
Share this page LinkedIn