Configuration Changes and Their Impact on the SSR Cluster
Certain configuration changes made on an active SSR cluster may require you to shut down and reinitialize the cluster-for example, when the cluster geometry is changed or when modifications are made to the database schema. Here are some examples of configuration changes and their impact on the SSR cluster:
Dropping or adding of columns in the SSR database schema requires you to re-create the database by executing the request database delete database and then request database create database commands. It does not require shutdown of the cluster data nodes.
Changes to the SSR database schema requires you to restart all SRC components.
Moving from a two-node geometry to a four-node geometry, or vice versa, requires restarting of all management servers and data nodes in the SSR cluster by executing the restart component database command on each of the data nodes and management servers
Adding or removing client nodes requires restarting all management servers and the new client node (or shutdown the removed client node) in the SSR cluster by executing the restart component database command on each management server and the new client node.
To facilitate SSR maintenance, a command is used to set the SSR database into maintenance mode or production mode.
Modifying the SSR Database Schema in an Active Cluster (SRC CLI)
Modifying Attribute Mapping in an Active SSR Cluster (SRC CLI)