Open topic with navigation

# Clusters Grid

The Clusters grid presents definitions of persistence clusters and persistence services, along with selected details. In edit mode, you can add and delete persistence cluster and service definitions, and modify existing definitions.

For background information, see Persistence Services and Clusters.

For consequences of modifying this configuration, see Persistence Modifications: Store and Durable, and Quorum Behaviors.

## Levels

- Cluster
- Service Set
- Service

## Cluster Level

From the left menu, select Clusters.

Column | Description
--- | ---
Cluster | Required. Name of the persistence cluster. Cluster names must be unique within the realm. All names are limited to maximum length of 256 characters.
Last Modified | This timestamp indicates the date and time of the most recent change to this persistence cluster definition.
Disk Persistence Mode | Select the disk persistence mode. This option applies to replicated stores only. If you turn on disk persistence but have not turned on swapping, the messages are still held in memory. Once you turn on swapping, the messages are swapped out to disk and freed from memory. None Disable disk persistence. sync The client returns from a send-message call after the message has been written to a majority of disks. This mode generally provides consistent data and robustness, but at the cost of increased latency and lower throughput. If the cluster restarts, no data is lost; performance is subject to disk performance. async The client may return from a send-message call before the message has been written to disk by majority of the FTL servers. This mode generally provides less latency and more throughput, but messages could be lost if a majority of servers restart shortly after the API call.
DR Enabled | Disaster Recovery Replication In the GUI, select this checkbox to enable replication to the disaster recovery service set. In the web API, set this attribute to `true` to enable replication to the disaster recovery set.
DR Protocol | If you enable disaster recovery replication, the services in the cluster use this transport protocol to establish a communication bus for that purpose. You can set other parameters of the transport for each service in the cluster.
Primary Set | In the GUI, select one service set to be primary. In the web API, set this attribute to the name of the primary service set. The opposite service set is the standby set.

## Service Set Level

Each persistence cluster can contain either one or two sets of services. If the cluster enables disaster recovery replication, then configure two service sets. If the cluster does not enable disaster recovery replication, then only one service set is relevant. (See the DR Enabled column.) For background information, see Disaster Recovery.

Column | Description
--- | ---
Set Name | Name of the service set. You may use the default set names or supply other names. Set names must be unique within the cluster. All names are limited to maximum length of 256 characters.
Cluster Set Protocol | Persistence services with a cluster's service set communicate with one another using this transport. Select the transport protocol from the drop-down menu in this column. As needed, set the host, subnet, and port parameters in service-level columns. Set other parameters in the service details panel. Notice that all the services in a service set use the same cluster protocol, though individual services can supply different transport parameters. For connection-oriented protocols, such as static TCP, the realm service automatically arranges the listening ends and connecting ends.
Client Protocol | Client applications communicate with persistence services in the cluster using the client transport. Select the client transport protocol from the drop-down menu in this column. As needed, set the host, subnet, and port parameters in service-level columns. Set other parameters in the service details panel. Notice that all the services in a cluster use the same client protocol, though individual services can supply different transport parameters. For connection-oriented protocols, such as static TCP, the persistence service always is the listening end, and clients the connecting end.

## Service Level

If the cluster enables the disaster recovery feature, then each set must contain equivalent services. For background information, see Disaster Recovery.

Column | JSON Attribute | Description
--- | --- | ---
Service Name | `name` | Required. Name of the persistence service. Persistence service names must be globally unique within the realm. All names are limited to a maximum length of 256 characters.
Weight | `weight` | Optional. This value must be an integer in the range [1,10]. Larger values indicate greater preference that the service becomes the leader. When absent, the default weight is 10.
Cluster Host/Subnet Cluster Port |  | Persistence services inherit the cluster transport protocol from the service set. For connection-oriented transports, set the host name and port for establishing a connection (both are required). For dynamic TCP transports, you may set a subnet mask and port (both are optional).
Client Host/Subnet Client Port |  | Persistence services inherit the client transport protocol from the service set. For connection-oriented transports, set the host name and port for establishing a connection (both are required). For dynamic TCP transports, you may set a subnet mask and port (both are optional).
DR Host DR Port |  | Persistence services inherit the disaster recovery transport protocol from the cluster. Set the host name and port for establishing a connection (both are required).

Did you find this helpful?

Yes No
Great!
Thanks for taking the time to give us some feedback.
Sorry about that

Why wasn't this helpful? (check all that apply)

Could not find what I was looking for
Instructions confusing or unclear
Instructions did not work

Want to tell us more?

Please select at least one option or provide details about the issue!!

Error occurred while submitting feedback.

Error2 occurred while submitting feedback.

TIBCO FTL® - Enterprise Edition

Copyright © 2009-2024. Cloud Software Group, Inc. All Rights Reserved.