Skip to main content


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

Configuring session affinity for slow drain

Updated on July 8, 2022

Session affinity is configured with the load balancer. Session affinity ensures that all requests from a user are handled by the same Pega Platform server.

Session affinity is required in the load balancer for both slow drain and immediate drain quiesce. Immediate drain is the default quiesce method. Pega Platform settings related to cookie invalidation are applicable only for slow drain.

Production load balancers offer a range of options for configuring session affinity. Pega Platform supports cookie-based affinity for slow drain quiesce. For more information, see Quiescing nodes with slow drain. Configure cookies for high availability session affinity for slow drain quiesce by using the settings listed in the following table.

SettingDescription
session/ha/quiesce/customSessionInvalidationMethod
  • Value – configurable-cookie-invalidator or fully qualified class name of a class implementing the SessionInvalidationMethod in prpublic
  • 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
    • Set to the fully qualified name of a class implementing the interface SessionInvalidationMethod in prpublic
session/ha/quiesce/cookieToInvalidate

  • Value – Name of the cookie to invalidate
  • Functionality – Name of the cookie to invalidate when using the configurable-cookie-invalidator customSessionInvalidationMethod

    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