Discussion3Replies139Views JonnyGar Member since 2009 91 posts BNY Mellon Posted: 5 years agoLast activity: 5 years 6 months ago Closed Why are requestors for the pzHTTPLuceneSearch passivated?Spun off from When are passivated requestors restored?On a our dedicated search node (on Dev), I saw 1,432 passivated requestors here in the passivation table.This looks like the Soap service for Lucene search, pzHTTPLuceneSearch. I have no doubt, since I see the same collection of pages in a requestor in the requestor lists.This is a stateful service with a requestor pool. It looks like these requestors are getting passivated to the database. What's the value in that? (perhaps you are doing this to cache search results)(Granted, since this is the search node for Dev, it's not a big deal; and I hear search is changing in ML8 to Elastic search) System Administration ×Close popoverFacebookTwitterLinkedinEmail Copy Link Copied! Moderation Team has archived post This thread is closed to future replies. Content and links will no longer be updated. If you have the same/similar Discussion, please write a new Discussion. Posted: 5 years agonistr PEGA replied to JonnyGarThe service should be stateless. Please see if you can change it stateless and that helps.ElasticSearch is already available in 7.1.7 (ML7) of the Pega 7 platform. This does not use HTTP / SOAP requestors like Lucene for searches. Posted: 5 years agoJonnyGar BNY Mellon replied to nistrThanks! Trying that.Looks like historically this package has been Stateful. Posted: 5 years agonistr PEGA replied to JonnyGarYes. But it should not be. With Elastic Search in 7.1.7, these service packages are no longer used once the indices are built with Elastic Search.That said, did changing it to stateless work for you?