What affect does the TIBCO Data Virtualization config item "Weight of time keeper" have on the cluster and the time keeper node?

How does the weight of time keeper affect its participation in triggered tasks in TIBCO Data Virtualization?

For triggered requests that have been configured by the trigger to fire "Only once per cluster", there is normally a round-robin rotation to select a node in the cluster to perform the task of the request at the time of each trigger firing. This "Weight of time keeper" setting determines the frequency that a time keeper node would be chosen to perform the triggered request task, for each round robin rotation of all the nodes.


Example affects of various settings for "Weight of time keeper"
0 - the time keeper will never be chosen in the rotation.
1 - this is the default setting, and the time keeper node will participate equally with all the other nodes, once per rotation.
2 -  the time keeper will be chosen 2x as many times per rotation.
3 -  the time keeper will be chosen 3x as many times per rotation.

In other words, a setting of 2 in a cluster of 3 nodes means that the time keeper node will be chosen 50% of the time per rotation, while a setting of 2 in a cluster of 4 nodes means the time keeper node will be chosen 40% of the time for each rotation.