Posted: 3 Jan 2017 0:49 EST Last activity: 31 Aug 2017 20:47 EDT
Disabling both Lucene and Elastic Search in Production
We are planning to disable both the Lucene search as well as Elastic Search in Production as we don't require it. My query is if we just disable the "Enable Indexing, All Rules, All Data and All Work" in the System: Settings -> Search landing page is enough or still should I go ahead and disable the FTSIncrementalIndexer agent as well? Should I still worry about SystemIndexer and SystemWorkIndexer Agents as well? Bec I think The Pega-Rules Agent is of FINAL type.
indexing/distributed/enabled should also be set to false, else elastic search would be running (in the server) though no indexing would happen . Once this is set server need to be restarted in-order to stop ES node from starting.
SystemWorkIndexer should be left enabled, but FTSIncrementalIndexer and SystemIndexer could be disabled.
Thanks for your reply Othos. I'll set the indexing/distributed/enabled DSS to false.
But the Pega-Rules Agent is final right. Hence I may not be able to disable the SystemIndexer Agent. I think the only possible way is to disable the Schedule but it is not possible because there are many nodes in Prod. Should we really consider disabling the Agents (FTSIncrementalIndexer and SystemIndexer )? Or mere disabling the above DSS and "Enable Indexing" in Search tab is enough?
What's the reason for leaving SystemWorkIndexer enabled? when you stop whole indexing and full text search on the system, how does this agent run ? I'm seeing the exception below, when I disabled FTSIncrementalIndexer ,SystemIndexer and enable just SystemWorkIndexer so I believe running this agent is not required.
Agent Pega-RULES #5: System-Work-Indexer.SystemWorkIndexer encountered an execution error. Restarting after delay. Exception at 20170901T003221.094 GMT: java.lang.NullPointerException at com.pega.pegarules.session.internal.mgmt.Executable.runIncrementalIndexer(Executable.java:11062) at com.pegarules.generated.activity.ra_action_systemworkindexer_fff8383320e9fddc873150b930f50b95.step1_circum0(ra_action_systemworkindexer_fff8383320e9fddc873150b930f50b95.java:161) at com.pegarules.generated.activity.ra_action_systemworkindexer_fff8383320e9fddc873150b930f50b95.perform(ra_action_systemworkindexer_fff8383320e9fddc873150b930f50b95.java:69) at
Additional information - I believe SystemIndexer is obsolete and FTSIncrementalIndexer replaced it. So the discussion should be on....after full text search is disabled on your system using DASS(indexing/distributed/....) - should both FTSIncrementalIndexer and SystemWorkIndexer agents still run ? thanks
Cool. I did that but the normal search is not working fine. The moment i disable the "Enable Indexing" check box in the System: Settings landing page, the search is not working as normal (along with the old: keyword as well). It is giving the same results for everything. Am I missing something? Please find attached image for an example search and the settings.
Hi, I didn't get your use-case; you want to disable lucene and elastic but still want to search ?
indexing/enabled are master settings which will control whether search would be available. Hence when the settings are disabled, you wont be able to perform search as well. Probably if you could tell us your exact use-case i.e. you still want to search against database, we can help
We just need to disable the indexing part as the tables PR_SYS_WORKINDEXER_QUEUE and PR_SYS_QUEUE_FTSINDEXER are growing a lot in Production. Hence we thought of disabling the search index. But still we need to search for rules in Production without using the indexing mechanism.As per my understanding, disabling the indexing should not affect the search of rules only that the call will go to the DB direclty instead of the indexed location.