Question1Replies526Views GunawanD Member since 2013 14 posts Accenture Posted: 3 years agoLast activity: 3 years 2 months ago Closed Zero Downtime DeploymentOn Section: Performing a rolling restart in a highly available system under https://pdn.pega.com/documents/pega-72-high-availability-administration-guide, it explains how to achieve zero downtime.For the following scenario:Before deployment, user are on server1 using ruleset 01-01-01.Proceed to perform rolling restart (quiesce user) on server1, user will then be moved to server2 using ruleset 01-01-01.Import ruleset 01-01-02 on server1, this will be propagated to server2, however application will still use ruleset 01-01-01. At this point, new user login to server2 will still useruleset 01-01-01Restarted server1 and start serving requests.Proceed to quiesce users on server2 using ruleset 01-01-01 and move users to server1.We are trying to achieve zero downtime deployment in the event that server restart is required (e.g. table structure changes, etc.)Questions:1. At point #4, how do we make sure new users on server1 will use ruleset 01-01-02 while users on new users on server2 will still use ruleset 01-01-01?2. At point #5, when users move to server1, what ruleset user will be using? Can we force it to use ruleset 01-01-02?Any idea? Low-Code App Development Installation and Deployment ×Close popoverFacebookTwitterLinkedinEmail Copy Link Copied! Moderation Team has archived post This thread is closed to future replies. Content and links will no longer be updated. If you have the same/similar Question, please write a new Question. Posted: 3 years agoHabeebBaig PEGA replied to GunawanDProbably you differentiate ruleset version with different access groups as you can associate a particular ruleset version in access group from advanced tab of the access group rule.