Persistence Cluster Details Page

Use this page to view detailed information about a persistence cluster or perform actions on the persistence cluster.

Persistence Cluster Actions

Action Description
Suspend Cluster

Suspend all services in the cluster, in preparation for saving the contents of its persistence services. For background information, see [Saving and Loading Persistence State], and its subtopics. You need to manually restart all persistence services to bring the cluster back online.

This command is used only when disk persistence is disabled.

Save Cluster

Save the data state of all the persistence services in the cluster. This command is visible only after suspending the persistence cluster. For background information, see [Saving and Loading Persistence State], and its subtopics.

This command is used only when disk persistence is disabled.

Force Quorum Formation Force this cluster to form a quorum. This command is visible only when it is relevant. Before using this command, read [Before Forcing a Quorum].
Backup Cluster Back up the disk(s). When disk persistence is enabled, this command backs up the files associated with disk persistence. See [Disk Persistence Backup and Restore].
Begin Online Compaction

Instruct all members of the persistence cluster to begin a disk compaction. If there is not enough disk space, the persistence service will not start compaction, and will log an error message. For details, see [Compact Disk Persistence Files with Persistence Service Online].

This command is used only when disk persistence is enabled.

Quorum Member Details

This table lists each persistence service in the persistence cluster.

Field Description
Server Disk Usage

The amount of disk currently in use for storing messages and acks, followed by the amount of disk allocated by this persistence service.

As messages are consumed, the amount of disk in use will generally decrease. For performance reasons, however, the persistence service will not immediately release disk space to the OS.

If the amount of disk in use is close to the amount of disk allocated, the persistence service may soon allocate more disk, increasing disk usage on the system.

If the amount of disk in use is much lower than the amount of disk allocated, a compaction may release disk space to the OS.

System Disk Usage

For the filesystem where the persistence service’s data directory is located, this is the total amount of disk used, followed by the total disk capacity.

If the amount of disk used is close to the disk capacity, the persistence service may soon stop accepting new messages.

Msg/s In

Inbound message rate for the persistence service, expressed as a number of messages and a number of bytes.

Note: Only the leader has a non-zero value.
Msg/s Out

Outbound message rate for the persistence service, expressed as a number of messages and a number of bytes.

Note: Only the leader has a non-zero value.
Disk Read Op/s Disk read rate for the persistence service, expressed as a number of reads and a number of bytes.
Disk Write Op/s Disk write rate for the persistence service, expressed as a number of writes and a number of bytes.
Quorum Number A count that increments every time a leader is elected. During normal operation, all members have the same quorum number.
Quorum Version A count that increments every time a message, ack or other information is replicated. During normal operation, all members have approximately the same quorum version.
Disk Sync Op/s File sync rate for the persistence service, expressed as a number of file sync calls.
Transport Bytes Sent/s

Network send rate for each of the persistence service’s transports:

  • Client: data exchanged with client applications (inbound and outbound messages).

  • Cluster: data exchanged between persistence services (replication of messages, heartbeats, etc).

  • DR: data exchanged with the disaster recovery site.

  • Inter-Cluster: data exchanged over routes to other persistence clusters in a forwarding zone.

Transport Bytes Received/s

Network receive rate for each of the persistence service’s transports:

  • Client: data exchanged with client applications (inbound and outbound messages).

  • Cluster: data exchanged between persistence services (replication of messages, heartbeats, etc).

  • DR: data exchanged with the disaster recovery site.

  • Inter-Cluster: data exchanged over routes to other persistence clusters in a forwarding zone.

Action Description
Change Log Level

Change the logging level of a persistence service.

For the meaning of log level values, see [Log Level Reference] in TIBCO FTL Development.