Skip to main content


         This documentation site is for previous versions. Visit our new documentation site for current releases.      
 

This content has been archived and is no longer being updated.

Links may not function; however, this content may be relevant to outdated versions of the product.

Quiescing nodes with slow drain

Updated on April 5, 2022

Slow drain for quiesce on a highly available system is not the default. The following actions occur on a Pega Platform server when the quiesce process is enabled.

  • The default time-out for passivation is reduced, referred to as an accelerated passivation period.
  • Users are placed in a passivation queue.
  • The system stops non-essential agent processing for quiesce and all listeners, with the exception of message-driven bean (MDB) listeners.
    Note: System critical agents remain active during this step.
  • When the active user requestor count drops to 0, the system sets the server state to "Quiesce Complete" and the Pega Platform server is ready for maintenance.

For a diagram that illustrates the on-premises quiesce flow for highly available systems when using slow drain, see Slow drain quiesce flow.

Have a question? Get answers now.

Visit the Support Center to ask questions, engage in discussions, share ideas, and help others.

Did you find this content helpful?

Want to help us improve this content?

We'd prefer it if you saw us at our best.

Pega.com is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us