We're looking to programmatically stand up a new Pega cluster and want to follow the constraint that a 2nd node with Search node type can not be added until the "All rules" and "All data" indexes show as "AVAILABLE" on the 1st Search node.
The only documentation I can find says to use the UI, but the UI data has to be coming from somewhere. Is there a database table we could query to confirm the ElasticSearch indexes are "available"? Or a file to look at on the server?
This documentation talks about how to manually confirm indexes available by going to Configure > System > Settings > Search. This will not work for our use case.
Also, I tried using the LiveUI tool to track down the pyIndexState property that is displayed on the Search Landing page but couldn't find a database mapping or data transform.
May I know the reason to have this constraint on the addition of the 2nd search node?
How a search node is added from a script?
As far I know platform relies on a logic built around elastic search APIs to know the status of indexing, in short, it is not directly available in a script because the state is not present in the database and ES rest endpoints are disabled by default.