After requestor timeouts happen, the page data (System-SavedPages) and requestor info (System-Requestor-Context) get saved into either filesystem or database depending on the settings. There is an out-of-the-box Agent called "PassivationDaemon", which periodically checks the old passivation data and purge it for clean up.
(1) Does this "PassivationDaemon" only purge its own app server's data on database table (PR_SYS_CONTEXT for requestor, and PR_PAGE_STORE for page data)? i.e. Agent resides on multiple nodes. Agent on app node #1 only deletes rows in table and won't delete rows that was created from other node?
(2) Does this "PassivationDaemon" work on database tables? Or, if the setting is "filesystem", does it clean up files under tempDir/PassivationData directory on its own app node?