Add or delete persistence clusters
|
You can add, rename, or delete a persistence cluster.
You cannot delete a cluster definition while any of its persistence services are running.
Renaming a cluster is equivalent to deleting and re-adding the cluster definition.
|
Add or delete persistence stores
|
You can add, rename, or delete a persistence store.
Deleting a store discards all messages in the store.
Renaming a store is like deleting it and creating a new,
empty store.
Before deleting or renaming a store, you must first review every application definition in the realm, ensuring that none of the endpoints still refer to the store you plan to delete.
After deleting or renaming a store, all the persistence services in the cluster require restart.
- Use the FTL server interface to stop one persistence service. The FTL server will automatically restart that persistence service.
- Wait for the new persistence service to synchronize with the existing services.
- Repeat for each persistence service in the cluster.
|
Add or delete durables
|
You can add durables to a store, or delete durables from a store.
(When deleting a static durable from a store, you must also remove subscriber name mappings to that durable.)
|
Modify store or durable parameters
|
You can modify parameter values of stores and durables.
When modifying the publisher mode of a store, or the acknowledgment mode of a durable, all affected clients disconnect from the cluster (that is, the leader) and automatically reconnect.
From the moment that a subscriber object first interacts with a durable, you may no longer change a durable’s message interest, nor its matcher fields. If these configuration values must subsequently change, you can instead map the subscriber to a new durable with the correct message interest and matcher fields.
|
Modify the mapping from subscriber names to durables
|
You can modify the mapping from subscriber names to static durable names for an endpoint.
|
Add dynamic durable templates
|
You can add dynamic durable templates and associate endpoints with the new templates.
|
Modify or delete dynamic durable templates
|
You can modify or delete dynamic durable templates. You can associate an endpoint with a different dynamic durable template. All clients that have durable subscribers on an affected endpoint require restart.
|
Add or delete persistence services
|
You can add a persistence service. You can delete or rename a persistence service only if none of the services in the cluster are running.
Changes to persistence services in the realm definition usually entail parallel changes in the FTL server configuration file. Restart the FTL server to read its updated configuration file.
When adding a service, assign it a low weight, so that it does not immediately become the leader. You can raise its weight later, after it replicates the cluster’s message data.
While reforming a quorum the cluster temporarily becomes unavailable. Ensure that adding or deleting a persistence service does not prevent forming a quorum.
|
Modify cluster transport parameters of a persistence service
|
It is illegal to modify cluster transports of persistence services.
|
Modify client transport parameters of a persistence service
|
You can modify client transports of persistence services.
When modifying a primary client transport or any of its parameters, that persistence service and all its clients require restart.
- Stop the persistence service. The FTL server automatically restarts it.
- Wait for the restarted service to synchronize its data state with the remaining services.
- Restart all the clients of the restarted service.
- Repeat for each persistence service in the cluster for which you have modified a client transport.
|
Modify alternate client transport parameters of a persistence service
|
You can modify alternate client transports of persistence services.
Adding an alternate client transport that was not previously configured does not require restart. Clients can connect using that transport immediately following successful deployment.
Deleting an alternate client transport does not require restart. Clients cannot connect nor reconnect using the deleted transport. However, existing clients can remain connected on the deleted transport.
Modifying the transport parameters of an alternate client transport requires restart of the persistence service and the clients that connect using the modified transport.
- Stop the persistence service. The FTL server automatically restarts it.
- Wait for the restarted service to synchronize its data state with the remaining services.
- Restart all the clients of the restarted service.
- Repeat for each persistence service in the cluster for which you have modified a client transport.
You can add and delete associated client host names. The persistence service does not require restart. Clients on added hosts can connect using the alternate client transport immediately following successful deployment. A client on a deleted host remains connected until the client restarts. For example:
- If the alternate client transport already names host1 and you add host2, then upon deployment clients on host2 can connect using the alternate client transport.
- If the alternate client transport names host1 and host3, and you delete host3, then upon deployment clients on host3 remain connected using the alternate client transport. However, a client on host3 that stops and subsequently restarts can no longer connect using the alternate client transport.
|