How to configure the directory for filesystem HA passivation
Hi,
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.
https://docs.pega.com/pega-722-high-availability-administration-guide
This page in the help mentions the settings to set to use either database passivation or filesystem passivation but again doesn't tell you how to configure the directory for filesystem passivation.
https://community.pega.com/sites/default/files/help_v722/procomhelpmain.htm
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.
https://community.pega.com/sites/default/files/help_v722/procomhelpmain.htm availability/crash recovery/eng-high-availability-server-crash-recovery-con.htm
I should also mention that I am triggering a Quiesce via JMX before the Pega server is shutdown
What am I missing?
Thanks,
Joel
Hi,
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.
https://docs.pega.com/pega-722-high-availability-administration-guide
This page in the help mentions the settings to set to use either database passivation or filesystem passivation but again doesn't tell you how to configure the directory for filesystem passivation.
https://community.pega.com/sites/default/files/help_v722/procomhelpmain.htm
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.
https://community.pega.com/sites/default/files/help_v722/procomhelpmain.htm availability/crash recovery/eng-high-availability-server-crash-recovery-con.htm
I should also mention that I am triggering a Quiesce via JMX before the Pega server is shutdown
What am I missing?
Thanks,
Joel
***Updated by moderator: Lochan to add documentation bug ID***
***Updated by Moderator: Marissa to add Doc Bug group tag***
**Moderation Team has archived post**
This post has been archived for educational purposes. Contents and links will no longer be updated. If you have the same/similar question, please write a new post.
Accepted Solution
Pegasystems Inc.
IN
Hello!
The documentation bug is fixed in the Pega 7.3 Help file: https://community.pega.com/sites/default/files/help_v73/procomhelpmain.htm availability/crash recovery/eng-high-availability-server-crash-recovery-con.htm
Regards,
Pegasystems Inc.
US
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.
IP Australia
AU
Hi Kevin,
Thanks for your reply, I'll try out crash recovery and see how it goes.
Do you know what is required to make filesystem passivation work though?
I'm not sure why I wasn't able to change the location.
PEG
GB
Perhaps it's too late in the week, but I didn't see the config setting in the link
However, in my environment I have "storage/class/passivation:/rootpath" and I have previously quiesced nodes via the filesystem and my operator session was successfully transferred to another node.
Did you include the colon in your setting name?
IP Australia
AU
Where did you find out that a colon is necessary?
There is no colon in the help file, is that a documentation bug?
https://community.pega.com/sites/default/files/help_v722/procomhelpmain.htm availability/crash recovery/eng-high-availability-server-crash-recovery-con.htm
Hmm, this pdn article has a colon too.
Do I need to raise a support request to fix the documentation?
Pegasystems Inc.
IN
Hello,
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.
Regards,
IP Australia
AU
It looks like https://docs-previous.pega.com/pega-72-high-availability-administration-guide has the colon in it and is correct but https://pdn.pega.com/documents/pega-722-high-availability-administration-guide doesn't.
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?
It looks like https://docs-previous.pega.com/pega-72-high-availability-administration-guide has the colon in it and is correct but https://pdn.pega.com/documents/pega-722-high-availability-administration-guide doesn't.
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
implementation using Memcached.
Pegasystems Inc.
IN
Hi Joel,
We would recommend you to talk directly to the Pega Academy team by posting your question on the Pega Academy Community right here on PDN: https://collaborate.pega.com/discussion/pega-academy-down
You could also send them feedback directly: https://academy.pega.com/contact
I could branch your reply above to a new post on the Academy community but I believe having you post the question would be simpler and more effective!
Thank you,
PEG
GB
Thanks for letting us know about the problem with the on-line documentation.
I'd previously preferred to one of the High Availability guides for the format. Such as: -
https://docs-previous.pega.com/pega-72-high-availability-administration-guide
Accepted Solution
Pegasystems Inc.
IN
Hello!
The documentation bug is fixed in the Pega 7.3 Help file: https://community.pega.com/sites/default/files/help_v73/procomhelpmain.htm availability/crash recovery/eng-high-availability-server-crash-recovery-con.htm
Regards,