Question
Netcompany
GB
Last activity: 25 Jan 2024 3:22 EST
Creating new web nodes in 8.7.2 customer cloud
Hello,
We are attempting to upgrade java and Tomcat in our web nodes, to do this I have attempted to create an AWS deployment template from one of the old web nodes.
The steps I have taken are
taken the snapshot,
deployed a new server with the same connectivity,
changed the setenv.sh file to now give the webnode the AWS instance ID
Started Tomcat.
When the server starts, the application is available, the server can reach the stream servers and everything appears normal.
However Indexing for this particular node remains unavailable.
Is there a setting that needs to be changed somewhere to increase the amount of web nodes being served?
Or is there something I can clean out of my template to allow it to start indexing from scratch?
For obvious reasons it makes more sense to do this templated upgrade as i can retire the old webnodes individually once we have the new ones in place.
Currently running 8.7.2 for context.
Accepted Solution
Updated: 25 Jan 2024 3:22 EST
Pegasystems Inc.
GB
@AdamC16880652 there are a few settings that you might need to adjust. First, ensure that the new node is correctly added to the Elasticsearch cluster. You can do this in the Search index host node setting. If the issue persists, you might need to manually set the minimum number of indexing host nodes required to be online for Elasticsearch. You can do this by setting the Dynamic System Settings (DSS) 'indexing/distributed/auto_minimum_master_nodes' to true and 'indexing/distributed/minimum_master_nodes' to your desired minimum. Also, ensure that the indexes are hosted locally on the server that is hosting the application server, rather than on a network drive. Lastly, ensure that the necessary TCP ports are open for communication between nodes. By default, ports in the range of 9300-9399 are used for Elasticsearch.
Based on the information provided, it seems like the issue might be related to the Elasticsearch configuration. When you create a new node, you need to ensure that the Elasticsearch settings are correctly configured. This includes making sure that the new node is correctly added to the cluster and that the necessary ports are open for communication between nodes. You might also need to check the prconfig.xml file to ensure that the correct settings are in place for the new node. If the issue persists, you might need to manually restart Elasticsearch or perform a re-indexing operation. Please remember to back up your data before performing any major operations.
@AdamC16880652 there are a few settings that you might need to adjust. First, ensure that the new node is correctly added to the Elasticsearch cluster. You can do this in the Search index host node setting. If the issue persists, you might need to manually set the minimum number of indexing host nodes required to be online for Elasticsearch. You can do this by setting the Dynamic System Settings (DSS) 'indexing/distributed/auto_minimum_master_nodes' to true and 'indexing/distributed/minimum_master_nodes' to your desired minimum. Also, ensure that the indexes are hosted locally on the server that is hosting the application server, rather than on a network drive. Lastly, ensure that the necessary TCP ports are open for communication between nodes. By default, ports in the range of 9300-9399 are used for Elasticsearch.
Based on the information provided, it seems like the issue might be related to the Elasticsearch configuration. When you create a new node, you need to ensure that the Elasticsearch settings are correctly configured. This includes making sure that the new node is correctly added to the cluster and that the necessary ports are open for communication between nodes. You might also need to check the prconfig.xml file to ensure that the correct settings are in place for the new node. If the issue persists, you might need to manually restart Elasticsearch or perform a re-indexing operation. Please remember to back up your data before performing any major operations.
Please see the 'index' fixes in Pega 8.7.4 Resolved Issues
⚠ This is a GenAI-powered tool. All generated answers require validation against the provided references.
Preparing to configure an Apache Tomcat application server
Troubleshooting Elasticsearch issues in Pega 7.1.7 through 8.8.3
Unable to start up Pega 8.5.2 on AWS Tomcat postgres
Rebuilding search indexes by using a direct connection to the database
If you still need help, please can you log a support incident via the MSP, and please provide the INC id here so that we can help track it.