High availability - filesystem vs. database choice
Hello
I am getting up to speed on HA configuration. I am reading the 7.22 Administration guide, and in the Shared storage section, I find the following statement:
When high availability is enabled, database passivation is used as the default passivation method, in
which the database handles all storage requirements.
However, if you decide to instead use filesystem passivation, you must select a shared storage solution
and need to implement the shared storage API to integrate with the Pega 7 Platform.
Looking for some guidance on what factors would drive you to use filesystem passivation vs. database passivation. Database seems like the natural choice.
TIA
Diane
Pegasystems Inc.
IN
In the database passivation, only the overhead will be the passivated requestor information will be stored in database and when required server will retrieve this information from database.
In the shared folder, it will be stored in the server's shared folder and there is no need to retrieve from db. But if there are numerous passivated requestors, then it consume a lot of memories and can lead to OOM issue.
Depending on the requestors and above mentioned factor, we need to decide .
Hope this helps.
Pegasystems Inc.
US
yes it does... thank you!
Pegasystems Inc.
US
FYI: starting from 7.2, if HA is enabled, database will be used as the default passivation storage.