Posted: 29 Jan 2019 15:30 EST Last activity: 14 Jun 2019 11:15 EDT
Pega Platform 7.4 Search Index Rebuild With Multi-Node System
My apologies if this is in Pega Help somewhere but I was unable to find the answer to this exact scenario.
We have 2 nodes in a cluster of Pega 7.4. I want node 1 to be the only host node for now. Both nodes are shut down. Node 1 comes up. Search index for rules and data build successfully with node 1 as host node. I then start node 2. When it completes startup the rules index starts rebuilding with node 2 as the only host node. Is this expected behavior or is there a setting somewhere that I am unaware of?
Thank you for any suggestions!
***Edited by Moderator Marissa to update SR Details***
In search landing page you would need to specify the Node(s) you want to be a search node.
Say you have two nodes and you made one of them as search node then this node is your search index.
In a multinode cluster system, the index files required for search can be hosted on one or more nodes. To ensure high reliability and minimize search query downtime, configure at least two, and preferably three nodes as search host nodes.
Caution! If you define more than one host node, wait until the index files have been completely built on the first node before configuring additional nodes. Configuring an additional host node causes the index files to be replicated from the first node to the next node and you want to ensure that the files have been completely built on the first node before replicating them.
Your case it can happen if you have added both nodes here.
Hi Shekhar. After building data and rules, I am unable to search for anything with special characters, such as a partial RuleSet Version. We have not had a problem like this in the past. Any ideas? In this case, I am expecting to see 02-16-02 versions show up for several RuleSets in search results.
I have not checked the broken queue. Can you tell me where I can find that? Thank you.
I also noticed that in my host index settings only one of my nodes is a host now when both were before. We still get search issues with rules not showing up on the node that is currently a host. I am adding the other node as host now.
1. Checked pr_sys_statusnodes. Both nodes have pyindexerstate active. The pyindexdirectory is correct for one of the nodes and NULL for the other node. Based on video 2 this seems okay. IP addresses are also okay.
2. Checked logs for "Master node unreachable" error. This error is not happening.
3. Confirmed FTSIndexer agent is running and that there are 0 pending items in the queue. When I import a RAP, the queue increases in size, and then decreases back to 0 with a little time as expected. This would lead me to believe the items are being added to search, but I still cannot see them on all nodes in the multinode environment.
4. Confirmed rules and data indexing are available not not negative values.
I'm not sure what to try from here. Do you have other ideas? Should I open an SR?