Regarding stopping Rule Indexing and Data Indexing In Production Environment as no one is searching rules(except prod support team) or data objects in production environment, so suggested to stop these indexing (by stopping system indexer agent) as putting huge load on server and impacting performance.
Do you see any issues if data indexing is stopped such as look up cache for worklist,workbasket not working. Can we stop these indexing in PROD ?
You cannot stop the FTSIncrementalIndexer from running if you're still using search for Work. If you did, no updates to existing work objects or newly created work objects will be indexed. You could disable Rule and Data indexing (unchecking the check boxes on the Search landing page and submitting the change), but the FTSIncrementalIndexer would still need to run (on all nodes to distribute work load). Disabling Data indexing should have no effect on anything cache related.
In a production environment, if you believe the FTSIncrementalIndexer is consuming a lot of resources, it's likely more related to the amount of new and updated work objects than rules and data. And again, ensuring the agent runs on all nodes should distribute the load.
Sorry, it wasn't clear what version of Pega you were on. I'm not as familiar with the 6.x series, but from what I can find in the help...
The SystemIndexer agent is responsible for updating Rules- and Data- indices, and the SystemWorkIndexer agent is responsible for updating Work- indices.
So it seems like you could disable indexing for Rules and Data and also the SystemIndexer agent to meet your requirement, however I would still advise testing this in lower environments to be sure it doesn't have some negative impact.
we would not be able to search rules properly in prod environment (if we stop rule indexing),if there is any investigation required by Production Support team based on live user session, How can we optimize(rule index stop or not stop) in this scenario?