Servers List
To see more details about a persistence server, click its row in the persistence clusters status table.
Columns
| GUI Item | Description |
|---|---|
| Server Status | Status of the persistence server process (as a string). |
| State | If the server is running, this string indicates its state or role with respect to the quorum and disaster recovery. For explanations of these state values, see Persistence Server States. |
| Name | The name of the persistence server. To see more detailed information about the server process, click this name. |
| ID | Client ID of the persistence server process (as a client of the realm server).
Administrators could use this client ID to retrieve client monitoring metrics about the persistence server using the realm server web API. |
| Set | The name of the disaster recovery server set to which this server belongs. |
| Host | The host name string of the persistence server’s host computer (if available). |
| History | This field indicates the data state of a server.
The first numeric value is the server’s quorum number. The second numeric value is the data state of the server. Higher values indicate more recent data. A history value of 0,0 indicates an empty server. |
| Consistency | This field indicates whether a server is up to date.
When the cluster does not contain enough up-to-date servers to form a quorum, administrators may force a quorum, using the most up-to-date server (see Before Forcing a Quorum). |
| Disk | When the server loads a state file from disk, or saves its state to disk, this JSON attribute reflects the state of the load or save operation. |
Commands
- Change logging level of a persistence server process.
For the meaning of log level values, see "Log Level Reference" in TIBCO FTL Development.
- Save the persistence server's data state to a file.
This command icon is visible only when the command is available. For background information, see Saving and Loading Persistence State and its subtasks.
Persistence Server States
| Role | Description |
|---|---|
| Leader | Functioning properly. This server is the leader. |
| Replica | Functioning properly. This server is a replica. |
| Offline | This persistence server is configured, but not connected to the realm server.
The process might have exited, or a network segmentation prevents connection. |
| Forming Quorum | This process is running, but the server is not yet functioning as part of a valid quorum.
If this state continues, ensure that all persistence server processes are running, and check network connectivity. |
| Timed Out | This persistence server had been connected to the realm server, but the realm server is no longer receiving heartbeat protocols from it. |
| Manual Intervention | Potential danger of data loss.
This server is the provisional leader, but it cannot safely form a quorum even though other servers are reachable. To proceed, see Before Forcing a Quorum. |
| Needs Restart | Warning.
The administrator is testing a deployment with configuration changes that would require this persistence server to restart. Meanwhile, this server is still functioning properly using the old realm definition. |
| Out of Sync | Error.
This persistence server is still functioning, but its realm definition is not the most recent deployment. (Even though the persistence server continues to function, this situation is an error, because the persistence server does not conform to the current configuration.) To use the new realm definition, you must restart the persistence server. Alternatively, you can roll back to the old realm definition by redeploying the previous deployment. |
| Exception | Recoverable error.
A non-fatal error occurred. After briefly registering this status, the persistence server will attempt to form a quorum. Check log files to determine the reason for the error. |
| DR Leader | Functioning properly. This server is the disaster recovery leader in the standby set. |
| DR Replica | Functioning properly. This server is a disaster recovery replica in the standby set. |