This topic describes how you can manage the cache server nodes in a cluster. This includes starting and stopping servers, adding and removing nodes, and moving a node.
For information about installing cache servers in a cluster, see Setting Up a Cache Server.
Cache servers determine the consistency of cached data between cache servers partially based on the timestamp used when storing and retrieving the data. As a result, all the clocks on all machines (both cache server machines and app server nodes) must be synchronized. It is common to do this through the use of an NTP daemon on each server synchronized to a common time source. You'll find a good starting point for understanding NTP at http://www.ntp.org/ntpfaq/. Note that clock synchronization becomes even more important when running within a virtualized environment; some additional steps may be required for proper clock synchronization as outlined in the vendor's documentation.
Also, if you're running in a virtualized environment, you must have VMware tools installed in order to counteract clock drift.
You can start and stop cache servers using the commands described below. Note that all cached data on that machine will be lost when its cache server is shut down.
On Linux /etc/init.d/jive-cache start
To stop a cache server use the following command:
On Linux /etc/init.d/jive-cache stop
Adding a cache server to a cluster that has existing cache machines requires additional steps beyond a fresh installation. In particular, you'll need to shut down the entire cluster (both application and cache servers) before you add a new cache server.
Removing a cache server from an existing cluster is very similar to adding one.
Moving a cache server from an existing cluster is very similar to adding a machine.