There may be scenarios where a working TIBCO Spotfire Statistics Services (TSSS) cluster using Multicast IP as the communication method stops functioning suddenly after environment specific changes done, which splits those machines to operate under multiple subnets. One of the common reasons is a change in the IP address for the Manager node machine and/or any worker node machine. The Multicast IP method only works if all the machines in the cluster are in same subnet.  

In such a case, browsing the "nodes" url (htttp://<serverhostname>:<port>/<servicename>/api/v8/nodes) for the cluster will not show the nodes from the different subnet, which will impact the overall job execution. In that example "nodes" URL, replace the following with the details from your installation:

• <serverhostname>: Hostname or IP address of Manager node or load balancer.
• <port>: Port being used by cluster.
• <servicename>: Name of the service being used for cluster

This may also be required if the cluster was incorrectly installed with Multicast IP communication method while installed on a cloud. You must specify JMS Messaging if your server is running on a cloud.

The solution in this scenario would be to switch to JMS Messaging communication method from Multicast. JMS supports communication between nodes over different subnets and will allow proper cluster operation on cloud installations..
 

This article describes detailed steps to change cluster communication method from Multicast IP to JMS (messaging) without need of reinstalling and configuring cluster again.

Steps to switch from Multicast IP to JMS Messaging:

1. Stop all Manager Nodes and Worker Nodes in the cluster.
2. From the cluster shared folder path, take a backup of the existing spserver.properties file which exists in the ‘conf’ folder.
3. Open original spserver.properties in text editor and make the following changes:

cluster.jms.port=3308

               3.4. After this change, these mentioned settings from spserver.properties should look like the those highlighted in the red rectangle in the attached screen shot (File: Switching_to_JMS_from_Multicast.PNG)
               3.5. Save the file.
     4. Restart all Manager nodes and Worker Nodes.
     5. Browse the ‘nodes’ url and verify it shows all the nodes in the cluster.
 

Doc: cluster.jms.port

• https://docs.tibco.com/pub/sf_statsvcs/7.11.0/doc/html/TIB_sf_statsvcs_7.11.0_installation/GUID-D618B433-4DC4-4590-B09E-67422F928D7C.html

KB: 000034778 TIBCO Spotfire Statistics Services Cluster on cloud environments must be configured with Messaging (JMS) as communication method

• https://support.tibco.com/s/article/TIBCO-Spotfire-Statistics-Services-Cluster-on-cloud-environments-must-be-configured-with-Messaging-JMS-as-communication-method​​