We get these logs hundreds of times per day. The curious part is that we are certainly NOT starting a quiesce. When this happens, it causes hundreds of alerts for writing pages into System-SavedPages which makes sense.
I'm wondering if there is any scenario where Pega will do this? Perhaps if it senses it encountered an internal issue...?
Environment: Pega 8.4.1, Jboss, Oracle DB, Redhat Linux
Hey Brett, when this issue happened yesterday, it was because the pingService had began not responding through our load balancer. It flagged unhealthy, so I went to see beneath the covers what was actually happening.
Getting at - the node wasn't showing at all in admin studio at this point. Then I circle back and think "I wonder if pega took itself out."
The value of initialization/persistrequestor may have been inadvertently changed to the value intended for initialization/persistrequestor/storage.
Normally initialization/persistrequestor is set to OnTimeout, which causes sessions to be passivated after 1 hour. Check the history of the setting to see if it's been updated. If you have another Pega system where you aren't seeing the passivation log messages, check the value of the setting there to compare. I don't think "Database" is a possible value for this setting.