Shutting Down the FTL Server Cluster

This section describes the methods available for shutting down an individual FTL server or an entire FTL server cluster, thereby shutting down any EMS servers running under those FTL servers.

Note: Killing an EMS server process is not supported. Since each EMS server runs as a service within an FTL server, killing an EMS server process will simply cause its hosting FTL server to automatically restart it.

EMS Administration Tool

The tibemsadmin tool can be used to shut down an individual FTL server. When connected to an EMS server that is using FTL stores, the tibemsadmin shutdown command will shut down both the EMS server and its hosting FTL server process.

See the Using the EMS Administration Tool section for a list of tibemsadmin options and usage instructions.

FTL Administration Tool

The FTL administration tool can be used to shut down an FTL server or FTL server cluster, thereby shutting down any EMS servers running under those FTL servers. This tool is available as part of the TIBCO FTL installation under FTL_HOME/bin/tibftladmin.

tibftladmin Options

The following table describes the tibftladmin options that are relevant to FTL stores.

Option Description
–-ftlserver url

URL of the FTL server to connect to. This URL can belong to any one of the FTL servers in the cluster.

URL must be in one of these forms:

http://<host>:<port>
https://<host>:<port>
--shutdown Shut down the FTL server process and all its services, including its associated EMS server.
–-shutdown_cluster

Alternative to the --shutdown option.

Shut down all FTL server processes in the cluster and all their services, including all associated EMS servers.

--tls.trust.file path Path to the trust file created in the Initializing FTL Server Cluster Security section. Required when connecting to a secure FTL server cluster.
--user user

User name to use when connecting to an FTL server cluster that has authentication enabled.

If the cluster’s authentication data was created based on the steps in Initializing FTL Server Cluster Security, the value passed to this option should be admin.

--password password

Password to use when connecting to an FTL server cluster that has authentication enabled. This should be the same password written to the users.txt file in Initializing FTL Server Cluster Security.

To hide the password from casual observers, see the Password Security section of the TIBCO FTL Administration guide.

Examples

 

Example 1

Shut down one of the FTL servers in the cluster: 

tibftladmin --ftlserver http://hostname:8080 --shutdown

 

Example 2

Shut down the entire FTL server cluster: 

tibftladmin --ftlserver http://hostname:8080 --shutdown_cluster

 

Example 3

Shut down a secure FTL server cluster: 

tibftladmin --ftlserver http://hostname:8080 --shutdown --tls.trust.file ftl-trust.pem --user admin --password password

Shutting Down and Restarting an In-Memory Cluster

When the in_memory_replication parameter is enabled, data is persisted only in-memory and is not written to disk. This means that performing a shutdown of the entire FTL server cluster by normal means would result in the loss of all FTL server state information – and thereby, all EMS server state information. To prevent this from happening, the cluster should only be shut down using the save_and_exit EMS administration tool command. This command will instruct each FTL server in the cluster to write its state to disk and then shut down. The state information for each FTL server will be written to a state file named <FTL server name>.state under its FTL store-specific data directory.

When the FTL server cluster needs to be restarted, the first step should be to modify the YAML configuration to instruct the cluster to load its saved state from disk upon startup. This can be done by adding the load parameter to the tibemsd service of each FTL server present in the YAML configuration. Each FTL server’s load parameter must be supplied with the absolute path to the matching state file that was generated during the cluster shutdown.

servers:
  <name of FTL server #1>
  # ...
  - tibemsd
      # ...
      load: <path to state file of FTL server #1>
  <name of FTL server #2>
  # ...
  - tibemsd
      # ...
      load: <path to state file of FTL server #2>
  <name of FTL server #3>
  # ...
  - tibemsd
      # ...
      load: <path to state file of FTL server #3>