Question
1
Replies
629
Views
CVS
Posted: November 20, 2015
Last activity: November 30, 2015
Closed
Are node level Data pages are stored in Shared Storage in Pega 7
Hello Everyone,
We came across a requirement , and would like to make use of Data Pages rather than Database Table to avoid expensive DB Calls. And what we are going to store on this Data page is the recent cards history of a CCP. I have below questions on this...
Are Node levelvdata pages stored in the shared storage, i.e. In a clustured env even if a JVM crashes, can we get this information from the shared storage.
If indeed they are stored in the shared storage, would they be copied to shared storage on a time to time basic or would they be stored in the shred storage from the very beginning.
Is it advisable to store huge amounts of data on a Data page in the shared storage.
Thanks,
Pradeep Gunda
Moderation Team has archived post,
Close popover
This thread is closed to future replies. Content and links will no longer be updated. If you have the same/similar Question, please write a new Question.
Please refer to this link regarding data page management: https://pdn.pega.com/data-management/how-pega-7-manages-data-pages. Here is the section that is relevant to your questions:
Passivation
Passivation allows the state of a Java object — such as an entire Pega 7 Platform PRThread context, including the clipboard state — to be saved to a file. A later operation, known as activation, restores the object.
The Pega 7 Platform uses standard passivation in general operation, but you can also configure passivation to shared storage in highly available environments. When all or part of a requestor clipboard is idle for an extended period and available JVM memory is limited, the Pega 7 Platform automatically saves clipboard pages in a disk file on the server. This action frees JVM memory for use by active requestors. (Typically, such passivation occurs only on systems that support 50 or more simultaneous requestors.)
The system passivates editable data page instances, but discards read-only data page instances.