Installing Secondary Servers

When installing a secondary server, you will need to specify several new arguments from the roles configuration.

Tip: While you can consult the Deployment > Roles tab in the Administration Console, you may find it easier to consult <DATADIR>/config/Deployment.xml on the primary server.

This task shows you how to:

See Also
High Availability with a Small Index
Full High Availability with a Large Index
Adding Hosts, Roles and Build Groups
Stop Applying Configurations to a Slave Host

Install the Secondary Server

  1. Make sure that the primary server is up and running.

    This is required because the primary server owns the configuration files required by the secondary server.

  2. Unpack the Exalead CloudView archive to the target directory.

    We recommend using the same installation path as for the primary server when installing Exalead CloudView. Having a different path will not affect the main features of the product but it will break the Java memory consumption metrics in the Monitoring Console.

    This will create your INSTALLDIR folder, which will have the same name as the archive file.
  3. Run the installation script for the secondary server.

    In the INSTALLDIR, run the install script. 

    <INSTALLDIR>/install.sh -license <LICENSE> -data <DATADIR> -host <SECONDARY_SERVER_HOSTNAME> 
-importSecurity <EXISTING_DATADIR/security> -install <SECONDARY_SERVER_INSTALL> 
-slave <PRIMARY_SERVER_GATEWAY_URL>

    Where:

    Variable Description
    <LICENSE> The path to the Exalead CloudView license file (cvlicense.dat).
    <DATADIR> Creates the specified directory during installation, to store the index and configuration data. Specify a new directory for <DATADIR>.
    Important: For ease of maintenance, keep the <DATADIR> path separate from the <INSTALLDIR> path.
    <SECONDARY_SERVER_HOSTNAME> The secondary server's hostname value in the primary server’s Deployment.xml
    <PRIMARY_SERVER_GATEWAY_URL> Use the format http://<PRIMARYSERVERHOSTNAME>:<BASEPORT+11>
    <SECONDARY_SERVER_INSTALL> The secondary server's install value in the primary server's Deployment.xml
    <EXISTING_DATADIR/security> The path to the existing installation's <DATADIR>/security directory. This argument is required if you have .NET connectors. It is used to import the security keys.

    The following samples show the install script and the Deployment.xml file configuration. 

    install.sh -license cvlicense.dat -data /cloudview/data 
-importSecurity /cloudview/data/security -install slave
-slave http://server001.exalead.com:10011 -host server02.exalead.com

    <DeploymentConfig xmlns="exa:exa.bee.deploy.v10" version="0">
  <Host hostname="server001.exalead.com" install="cvdefault" hostAgentPort="10009">
    <PortRange startPort="10000" lastPort="10099"/>
    <Role name="Master"></Role>
    <Role name="Indexing"></Role>
    <Role name="Converter"></Role>
    <Role name="DictionaryBuilder"></Role>
    <Role name="Index">
      <RoleAttribute name="buildGroup" value="bg0"/>
      <RoleAttribute name="instance" value="i0"/>
      <RoleAttribute name="runtimeConfig" value="system_io_caching"/>
      <RoleAttribute name="useSharedDir" value="true"/>
    </Role>
  ...
  </Host>
  <Host hostname="server002.exalead.com" install="slave" hostAgentPort="10009">
    <PortRange startPort="10000" lastPort="10099"/>
    <Role name="Index">
      <RoleAttribute name="buildGroup" value="bg0"/>
      <RoleAttribute name="indexSlice" value="0"/>
      <RoleAttribute name="instance" value="i1"/>
      <RoleAttribute name="runtimeConfig" value="system_io_caching"/>
    </Role>
  </Host>
</DeploymentConfig>

  4. Once the installation is complete, start Exalead CloudView. See Start the Secondary Server.

Start the Secondary Server

  1. For Microsoft servers, see how to start Exalead CloudView in Windows Post-Install Procedures.
  2. For Linux servers, go to <DATADIR>/bin and enter: ./cvinit.sh start

Verify Index High Availability

Context: This applies to all deployment scenarios in the guide except for the one shown in Recommended Deployment.

  1. Verify searching using the secondary server's index:
    1. Go to the Mashup UI on the secondary server.
    2. Search for a particular document you know exists.
  2. Stop the index on the secondary server.
    1. In the Administration Console Home page, go to the Process section.
    2. From the Host list, select the secondary server.
    3. Stop all index slices.
  3. Go back to secondary server's Mashup UI, and perform the same search.
    You must have the same results as before, since the secondary server's search server is now sending the query to the primary server's index.
  4. Stop the primary server's index:
    1. In the Administration Console Home page, go to the Process section.
    2. From the Host list, select the primary server.
    3. Stop all index slices.
  5. Go back to secondary server's Mashup UI, and perform the same search.
    You should not receive any results, since there is no index running on your deployment.