Question

11
Replies
1104
Views
JoelP701 Member since 2015 3 posts
IP Australia
Posted: 3 years ago
Last activity: 3 years 1 month ago
Closed
Solved

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://pdn.pega.com/documents/pega-722-high-availability-administratio…

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://pdn.pega.com/sites/pdn.pega.com/files/help_v722/procomhelpmain…

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://pdn.pega.com/sites/pdn.pega.com/files/help_v722/procomhelpmain… 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.

Low-Code App Development Installation and Deployment
Moderation Team has archived post
Share this page LinkedIn