About Saved Configurations

Exalead CloudView’s configuration defines the high-level functional setup of the product. For example, in /config/deployment.xml your Exalead CloudView installation's server deployment is defined through roles such as Indexing, SearchAPI, or ConnectorsServer.

In the running Exalead CloudView instance, these roles are mapped to running processes.

When you apply the configuration, Exalead CloudView checks the high-level configuration for errors, then computes a low-level configuration for each process, known as the GCT. This process is described below.

When Exalead CloudView applies a configuration, it does the following:

1. Checks the entire configuration store for errors.
2. Computes and creates a new version of the detailed configuration (the GCT).
3. The GCT contains a list of services that run on each process, the configuration of each process, and the configuration for dynamic interprocess configuration.
4. Saves the new version of the GCT and the current state of the configuration store for future rollbacks.
5. Sends the new configuration to all hosts on the Exalead CloudView cluster.
6. Dynamically reloads the configuration for the running processes.
   • If Exalead CloudView cannot dynamically load some configuration changes, it restarts the affected processes.
   • If some roles were added, Exalead CloudView starts the new processes.