Posted: 2 May 2017 19:10 EDT Last activity: 4 Feb 2019 14:10 EST
How to configure the directory for filesystem HA passivation
I'm trying to configure the directory that Pega uses for filesystem HA passivation, but I'm having no luck. Strangely the High Availability Guide is very light on for actual detail, it talks about filesystem passivation but doesn't actually tell you how to configure it.
I have database passivation working correctly, but I would like to get crash recovery working, which from my reading, requires filesystem passivation to be configured.
Reading the Crash Recovery help page talks about setting "storage/class/passivation/rootpath" to be the directory where passivation data is written to, however when I set that, nothing was written to that directory. By default, pega seems to write file passivation data to the temp directory, which doesn't make sense to me as that won't help other nodes in the cluster use that passivation data.
I believe the doc you quoted there is a bit misleading, for 7.2.2, as long as HA is enabled (session/ha/Enabled = true), the default passivation storage is set to database, that includes crash recovery meta data.
A documentation bug or enhancement can now be submitted right on this community! We have created a documentation bug on your behalf. The bug ID is listed under the Related Support Case Number field above. I will keep you posted on any updates that I receive on this bug.
Also, it seems that the training material is wrong too, a colleague of mine did the 7.1.6 System Administration course and that also is missing the colon, the file in question is Pega_SYSAD_716_StudentGuide.
Additionally, what is curious is that the student guide says you shouldn't use the database for passivation when you want high availability. Does that mean that something has changed since 7.1.6? Or is the student guide simply wrong?
Passivation is performed by a background daemon which runs periodically and looks up the idle
requestors and then moves data to the disk. When the data is again retrieved within 24- 48 hours this
data is cleared from the disk as well. Again we can customize the dynamic system settings to save it in a
database instead of disk (change prconfig/initialization/persistrequestor/storage to database instead
of filesystem). However, passivated data cannot be saved in the database for applications that require
high availability. When using disk, it uses the temporary file directory by default and we can use dynamic
system settings to set the directory location where we want these files to be saved (changing prconfig/storage/class/passivation/rootpath). High availability applications can also use custom
passivation mechanism by using custom classes to implement passivation. Look at the article titled
Creating a Custom Passivation method on the PDN that is in the related content for a sample