Shop

Your Notifications (0)

There are currently no notifications. You're all set!

Demos Trials
Knowledge Base
ChemDraw and ChemOffice+ Products Signals Notebook E-Notebook and ChemBioOffice Enterprise Spotfire and Signals Spotfire Products Columbus Signals Image Artist
Downloads
Downloads
Community
Support Forums Ideas Portal Product Basics
About Support
Legal Resources Support and Maintenance Plans Product Life Cycle Support News
Contact Support

Does a Cluster of TIBCO Spotfire Statistics Services (TSSS) support round-robin scheduling of jobs across its worker nodes?

Rich Talbot
  • Updated
Date Posted:
Product: TIBCO Spotfire®

Problem:

Does a Cluster of TIBCO Spotfire Statistics Services (TSSS) support round-robin scheduling of jobs across its worker nodes?


Solution:

A TIBCO Spotfire Statistics Services (TSSS) cluster with at least one Manager node and multiple Worker nodes will route jobs to available worker nodes for execution. From the TSSS jobs URL (http://<servername>:<port>/<ServiceName>/api/v8/jobs), you may see that all or most of the jobs get routed to only a single worker node, without routing jobs to other worker nodes. This may create confusion about whether the TSSS cluster is working correctly, and whether there is a configuration issue that prevents routing jobs to other worker nodes.

Note:  In the above jobs URL, replace <servername>, <port> and <ServiceName> as defined in your TSSS cluster installation.

  The clustering algorithm used in TSSS does not guarantee round-robin scheduling, but rather will fill one Worker with jobs before scheduling jobs to the next Worker. Clustering provides improved performance.  So the behavior mentioned above is expected, as long as the total number of engines available across the cluster is more than 0 and jobs are not queued extensively.
 
For example, with 2 Worker nodes in a cluster that has 4 engines available on each Worker node, if 4 jobs come in simultaneously, it is not a problem if all 4 of those jobs get allocated to the same Worker node. In this scenario, if 5 jobs come in simultaneously and 4 jobs get allocated to one Worker node, then the remaining (5th) job will get routed to the second Worker node. However, in this case if the 5th job gets queued without being routed to the other Worker node, then that is a cluster configuration issue that needs to be investigated.
  Doc : Cluster installation
https://docs.tibco.com/pub/sf_statsvcs/10.0.0/doc/html/TIB_sf_statsvcs_10.0_installation/GUID-1B0BECE1-01F8-4065-90DB-C1D84889A218.html

Doc : Manager nodes
https://docs.tibco.com/pub/sf_statsvcs/10.0.0/doc/html/TIB_sf_statsvcs_10.0_installation/GUID-08D696C8-2FC2-410B-92BD-414A32BC272C.html