FTSIncrementalIndexer should run on all nodes or only search node
We have 7 nodes in our PRPC 7.1.8 system, and we run indexing only on one node by giving only that node's node id in the search landing page. So question is should the agent FTSIncrementalIndexer run on all the nodes in the environment or only on the node where we setup search?
Accepted Solution
Tetrasoft India Private Limited
IN
Hi,
- FTSIncrementalIndexer takes care of keeping Rules, Data and Work indexes in sync.
- Whenever a rule, data or work instance gets inserted, updated or deleted in the DB, Pega creates an entry in the pr_sys_queue_ftsindexer table for the FTSIncrementalIndexer to consume. The agent runs every 60 seconds and drains the queue, figures out what needs to be indexed, opens the BLOB for each of the entries and updates the appropriate index accordingly.
- With FTSIncrementalIndexer agent running on all nodes, we are opening the instance from the DB on the node that is servicing the queue item. But the index files are updated only on the search node where the data is communicated between the node opening the instance and the node writing the index file.
Pegasystems
IN
Short answer: Run the agent on all nodes to process the changes faster. The agent takes care of updating the index only on the configured node as seen on the search landing page.
If FTSIncrementalIndexer is consuming a lot of resources impacting performance on nodes used by interactive users, then is it possible to run this only in Nodes set aside for non-interactive processing such as Agents (in general) and Listeners?
Pegasystems
IN
FTSIncrementalIndexer is an agent and thus the Data-Agent-Queue records can be modified to run only on only those nodes where you want them to run.
That said, we would like to understand why is FTSIncrementalIndexer consuming a lot of resources?