Cluster Details Panel
The Cluster details panel presents the details of a persistence cluster definition. In edit mode, you can modify the parameter values.
Heartbeats and Timeouts
You can adjust the persistence heartbeat and timeout parameters, which detect persistence service availability. For best results, use the default values, except to resolve specific issues or as directed by TIBCO personnel.
| GUI Parameter | Description |
|---|---|
| Service to Client
Persistence Heartbeat |
The leader persistence service sends heartbeats to its clients at this interval, in seconds. |
| Service to Client
Timeout Interval |
When the leader’s heartbeat is silent for this interval, in seconds, its clients seek to connect to a new leader from among the other services in the cluster.
When a client's heartbeat is silent for this interval, the persistence service clears all state associated with the client. |
| Service to Service
Persistence Heartbeat |
Persistence services in the cluster exchange heartbeats at this interval, in seconds. |
| Service to Service
Timeout Interval |
When the heartbeat of any service in the cluster is silent for this interval, in seconds, the remaining services attempt to form a new quorum. |
Message Swapping
You can enable or disable the ability for this cluster's store to use disk swap space when needed. Click the toggle switch to turn this feature on or off.
| GUI Parameter | JSON Attribute | Description |
|---|---|---|
| Message Swapping | disk_mode | Toggle switch to enable or disable message swapping for this cluster. The default setting is Disabled. Enabled is equivalent to disk_mode = swap. |
When message swapping is enabled, the server can swap messages from process memory to disk. Swapping allows the server to free process memory for more incoming messages, and to process message volume in excess of memory limit. When the server swaps a message to disk, a small record of the swapped message remains in memory.
Externally Reachable Addresses
When using persistence with zones of clusters that use an auto inter-cluster transport to address the cluster (or to address a load balancer's interface), use this field to identify one or more ports for the core servers of this cluster (or the port for the load balancer).