Replacing the primary node

If the master goes down permanently, you can replace the primary node.

To understand how Indexers function in a multiple-server deployment, see Indexer redundancy .

This topic contains the following information:

Replacing the primary node in an environment with existing Indexers

To replace the primary node in an environment where other Indexers already exist, you need to perform the following actions:

  • Turn one of the peer Indexers into the master.
  • Prepare the remaining peer Indexers to connect with the new master.
  • Prepare the the Console Server, Collection Station, and Search components in your environment to connect with the new master.

To replace the primary node in an environment with existing Indexers

  1. Go to the Indexer host that you want to turn into a master and perform the following steps:
    1. Navigate to %BMC_ITDA_HOME%\conf\indexer\elasticsearch.yml.
    2. Edit the elasticsearch.yml file and change the value of the following property to true:
      node.master: false
    3. In the elasticsearch.yml file,change the value of the following properties (if the values are set to localhost, then do not change the properties):

      network.bind_host: <FQDN>

      network.publish_host: <FQDN>
      Where, FQDN is the Fully Qualified Domain Name of the new master Indexer.

    4. Save the file
    5. Restart the Indexer. For more information, see Starting or stopping product services.
  2. Go to each of the remaining Indexer hosts (peers) and perform the following steps:
    1. Navigate to %BMC_ITDA_HOME%\conf\indexer\elasticsearch.yml.
    2. Edit the elasticsearch.yml file and change the value of the discovery.zen.ping.unicast.hosts property. The value of this property must be the host name and corresponding port number of the new master Indexer.
    3. Save the file.
    4. Restart the Indexers. For more information, see Starting or stopping product services.
  3. Go to the Collection Station instances in your environment and perform the following steps:
    1. Navigate to %BMC_ITDA_HOME%\station\collection\custom\conf\agent.properties.
    2. Edit the agent.properties file and change the value of the indexing.unicast.hosts property. The value of this property must be the host name and corresponding port number of the new master Indexer.
    3. Save the file.
    4. Restart the Collection Station instances. For more information, see Starting or stopping product services.
  4. Go to Search instances in your environment and perform the following steps:
    1. Navigate to %BMC_ITDA_HOME%\custom\conf\server\searchserviceCustomConfig.properties.
    2. Edit the searchserviceCustomConfig.properties file and change the value of the indexing.unicast.hosts property. The value of this property must be the host name and corresponding port number of the new master Indexer.
    3. Save the file.
    4. Restart the Search instances. For more information, see Starting or stopping product services.
  5. Go to the Console Server in your environment and perform the following steps: 
    1. Navigate to %BMC_ITDA_HOME%\custom\conf\server\olaengineCustomConfig.properties. 
    2. Edit the olaengineCustomConfig.properties file and change the value of the indexing.unicast.hosts property. The value of this property must be the host name and corresponding port number of the new master Indexer. 
    3. Save the file. 
    4. Restart the Console Server. For more information, see Starting or stopping product services.
     

Replacing the primary node in an environment with no other Indexer

To replace the primary node in an environment where no other Indexer already exists, you need to you need to perform the following actions:

  • Perform a custom installation of the new Indexer so that this Indexer functions as a master.
  • Prepare the Console Server, Collection Station, and Search components in your environment to connect with the new master.

To replace the primary node in an environment with no other Indexer

  1. Go to the host on which you want to install the new master Indexer.
  2. Perform a custom installation of the new Indexer. For more information, see Installing TrueSight IT Data Analytics in a multiple server environment using the wizard
    While performing the installation, ensure that you leave the Primary Node field blank.
  3. Go to the Collection Station instances in your environment and perform the following steps:
    1. Navigate to %BMC_ITDA_HOME%\station\collection\custom\conf\agent.properties.
    2. Edit the agent.properties file and change the value of the indexing.unicast.hosts property. The value of this property must be the host name and corresponding port number of the new master Indexer.
    3. Save the file.
    4. Restart the Collection Station instances. For more information, see Starting or stopping product services.
  4. Go to Search instances in your environment and perform the following steps:
    1. Navigate to %BMC_ITDA_HOME%\custom\conf\server\searchserviceCustomConfig.properties.
    2. Edit the searchserviceCustomConfig.properties file and change the value of the indexing.unicast.hosts property. The value of this property must be the host name and corresponding port number of the new master Indexer.
    3. Save the file.
    4. Restart the Search instances. For more information, see Starting or stopping product services.
  5. Go to the Console Server in your environment and perform the following steps: 
    1. Navigate to %BMC_ITDA_HOME%\custom\conf\server\olaengineCustomConfig.properties. 
    2. Edit the olaengineCustomConfig.properties file and change the value of the indexing.unicast.hosts property. The value of this property must be the host name and corresponding port number of the new master Indexer. 
    3. Save the file. 
    4. Restart the Console Server. For more information, see Starting or stopping product services.
Was this page helpful? Yes No Submitting... Thank you

Comments