Question
Agile Studio - Search Host Node settings do not stick, get blanked after server reboot
I have looked through similar posts related to the Search Index Host Node settings, but can't find my specific problem. We are using Agile Studio on Pega Platform 8.5.3. Every time the server is rebooted, the Host Node ID and File Directory (found here: Configure > System > Settings > Search in the "Search Index host node" setting section) are blanked out. I know how to enter the values, but is there a way to have these values populate automatically after a server reboot? We don't realize that the values are blanked until the Search function stops working or I check the values EVERY DAY to make sure they are there.
Proximus
BE
Hello,
Not sure about Agile Studio itself, but for PEGA search, with below parameters I've stabilized it.
have you defined the below for your processes?
-Dindex.directory=/YourFullPathPegaTempDir/PegaSearchIndex
-Didentification.nodeid=UniqueNameForYourProcess
Are you in cluster mode or single server mode?
If you're in cluster mode, then other servers should have below param -Dindex.directory= (keep it empty, so that search will not will initiated there)
And ideally, of course they all should have a unique Name for all other nodes.
What's NodeType Definition of this server, is Search defined for it ? And what's your application server type?
Regards
Anthony
California Department of Public Health
US
Thank you for the information.
It is a single server. Where does the -Didentification.nodeid=UniqueNameForYourProcess param go? Is there a config file that holds those params?
California Department of Public Health
US
Forgive me, but I'm fairly new to Pega and I do see that there is a Java VM Information section when looking at Node Information in Admin Studio. How does that Java VM Information get altered, specifically java.vm.args (which looks like is where the arguments/params are listed)?
Proximus
BE
well, this is the admin/technical part of your application.
I don't know whether you're on websphere, tomcat, or something else but these arguments are part of the process properties.
If you've got no idea on this setup then you'll need to find someone who can give you some info on your technical setup.
Regards
Anthony
Pegasystems Inc.
GB
@SonyaS12 as @Anthony_Gourtay has pointed out you can set the Host Node ID and File Directory values manually using JVM arguments.
For example, to set the node ID, you can use a JVM argument like -Didentification.nodeid=stream-node-1.
These values should be preserved after a server restart. If they are not being preserved, it may be worth checking your server's configuration and startup scripts to ensure they are being set correctly.
The Java VM Information, including java.vm.args, is determined by the Java Virtual Machine (JVM) arguments that are set when the Pega server node is started. These arguments are typically set in the configuration files of your application server (for example, setenv.sh for Tomcat) or as part of the startup command for your server. To alter these arguments, you would need to modify them in your application server's configuration and restart the server for the changes to take effect. Please note that changes to JVM arguments should be done carefully, as they can significantly impact the performance and behavior of your Pega application.
Viewing the JVM in use on your server
Preparing to configure an Apache Tomcat application server > Setting JVM par
@SonyaS12 as @Anthony_Gourtay has pointed out you can set the Host Node ID and File Directory values manually using JVM arguments.
For example, to set the node ID, you can use a JVM argument like -Didentification.nodeid=stream-node-1.
These values should be preserved after a server restart. If they are not being preserved, it may be worth checking your server's configuration and startup scripts to ensure they are being set correctly.
The Java VM Information, including java.vm.args, is determined by the Java Virtual Machine (JVM) arguments that are set when the Pega server node is started. These arguments are typically set in the configuration files of your application server (for example, setenv.sh for Tomcat) or as part of the startup command for your server. To alter these arguments, you would need to modify them in your application server's configuration and restart the server for the changes to take effect. Please note that changes to JVM arguments should be done carefully, as they can significantly impact the performance and behavior of your Pega application.
Viewing the JVM in use on your server
Preparing to configure an Apache Tomcat application server > Setting JVM par
Preparing your application server > Configuring Hazelcast to run on Java 11 or later
IF your issue is resolved can you please mark our forum user's reply with 'Accept Solution'?