01-06-2017 04:15 AM
We recently had a our Maintenance update from 9.4 M2 to 9.4 M3 . This a grid environment with 10 nodes of which only 9 are active and one active. This one inactive node was acting as metadata node earlier but later was changed. Currently our Metadata nodes are two nodes from our active nodes (including as failover). This being said the compute services script had to be changed and customized as per the grid. And the original script was considering the inactive node as the node name , before customizing.
Now with maintenance update in place , the initial configurations goess well, but while the time of SAS services to start , it fails to start Object spawner and other compute services.
Do let me know for any more details on the same . Appreciate your suppport.
01-06-2017 09:29 AM
01-06-2017 04:57 PM
I don't fully understand your question, but like Linus says, you should always try to add to the *_usermods files that are sourced by the main script where you can. If you want to modify a script that doesn't have a _usermods file you can always create one and source it in the same manner from the original script - this way, if it ever gets overwritten you will only ever have to add the line that sources it.
If you're looking to find out which of your spawners is the parent in a cluster you can get this from the spawner logfiles. This is a good read: