This site hosts historical documentation. Visit www.terracotta.org for recent product information.
Using the Terracotta Operations Center, a standalone enterprise-only console for operators, you can change the topology of a live cluster by reloading an edited Terracotta configuration file.
Note the following restrictions:
All servers and clients must load the same configuration file to avoid topology conflicts.
Servers that are part of the same server array but do not share the edited configuration file must have their configuration file edited and reloaded as shown below. Clients that do not load their configuration from the servers must have their configuration files edited to exactly match that of the servers.
To add a new server to a Terracotta cluster, follow these steps:
Add a new <server> block to the <servers> section in the Terracotta configuration file being used by the cluster. The new <server> block should contain the minimum information required to configure a new server. It should appear similar to the following, with your own values substituted:
<server host="myHost" name="server2" >
<data>%(user.home)/terracotta/server2/server-data</data>
<logs>%(user.home)/terracotta/server2/server-logs</logs>
<statistics>%(user.home)/terracotta/server2/server-stats</statistics>
<dso-port>9513</dso-port>
</server>
Open the Terracotta Operations Center by running the following script:
UNIX/LINUX
${TERRACOTTA_HOME}/bin/ops-center.sh
MICROSOFT WINDOWS
%TERRACOTTA_HOME%\bin\ops-center.bat
To remove a server from a Terracotta cluster configuration, follow these steps:
Open the Terracotta Operations Center by running the following script:
UNIX/LINUX
${TERRACOTTA_HOME}/bin/ops-center.sh
MICROSOFT WINDOWS
%TERRACOTTA_HOME%\bin\ops-center.bat
If you edit the configuration of an existing server and attempt to reload its configuration, the reload operation will fail. However, you can successfully edit an existing server’s configuration by following these steps: