Posted: 26 Oct 2017 11:27 EDT Last activity: 5 Dec 2017 7:14 EST
How ActiveNonQuiesceAdminUserCount is determined by Pega for High Availability Feature (Pega 7.1.8)
I am trying to implement High Availability in our platform. Can anyone please throw some light on how pega determines ActiveNonQuiesceAdminUserCount value. I have observed scenarios where the requestor management shows user logged-in count but ActiveNonQuiesceAdminUserCount value remains 0.
How Pega is able to determine which user is active and who isn't.
Second question would be how High Availability Cluster Management determines the node names available for a cluster of a Environment ?
I have been able to find out so far is a pega activity LoadClusterNodeList determines these values but still need to dig in more to understand it.
During the Quiesce Start run state Active Non Quiesce Admin User Count is a count of users that are still on the Pega 7 Platform server and have not been quiesced yet. Are you checking this value upon Quiesce start run?
Posted: 3 years ago
Posted: 5 Dec 2017 7:14 EST
Lochana Durgada Vijayakumar (Lochan_DV)
Lead Technical Documentation Specialist
KARANSTARZ has let us know that they have reached the below solution.
Operators with role as ̶PegaRULES:HighAvailabilityQuiesceInvestigator or pxQuiesceAdminControlOperators privilege are not quiesced along with other users and are not counted in the total number of active users on the node. So while testing High Availability feature make sure the test user does not have this role/privilege.