Upgrade the Multi-Node Events Service Cluster for Windows

This page describes the steps to upgrade the Events Service cluster having three or more nodes.

To upgrade a multi-node Events Service cluster, you require to create a temporary Windows instance and install the latest Enterprise Console. Use the Events Service binaries from the temporary instance to upgrade Events Service nodes in the cluster.

Perform the following steps to upgrade each Events Service node in the cluster:

  1. Create a temporary windows instance to install the Enterprise Console version that you want to upgrade.
    1. Select Custom Install.
    2. Specify the Platform name and click Create Platform.
      Specify the Platform Name.
    3. Go to Events Service, click Install.
      Install the Events Service.
    4. After Events Service is successfully installed and running, stop this Events Service.
      Stop the Events Service.
  2. Generate the events-service binary archive from the temporary instance.
  3. Stop and Back Up the Events Service Node.
  4. Update the Events Service Node.

Generate the events-service binary archive from the temporary instance

  1. Delete the following files and folders:
    • <APPDYNAMICS-HOME>\events-service\processor\elasticsearch\config\elasticsearch.keystore
    • <APPDYNAMICS-HOME>\events-service\data
  2. Compress the events-service folder to the zip file.
  3. Transfer the archived zip (events-service.zip) file to all the Events Service nodes in the cluster.
    Note: Do not copy the zip file to the existing Events Service path. You can copy this file to a temporary location on the nodes.

Stop and Back Up the Events Service Node

Follow the steps to stop and back up the Events Service node on the instance that you want to upgrade:
  1. Go to Enterprise Console, stop the Events Service. Alternatively, you can use the below command to stop the Events Service:
    cd <APPDYNAMICS-HOME>/events-service/processor/bin
events-service.exe stop
  2. Back up the existing events-service folder.
    <APPDYNAMICS-HOME>\events-service
    Note: Save this backup in a different path other than <APPDYNAMICS-HOME>. Then, delete the events-service folder from <APPDYNAMICS-HOME>.
  3. Ensure the same keys are on all the nodes. Check the keys in the below file:<APPDYNAMICS-HOME>\events-service\processor\conf\events-service-api-store.properties
    Verify the following keys have the same value in all the cluster nodes:
    Note: Specify the keys from the backup folder because they are unavailable in <APPDYNAMICS_HOME> after backing up and deleting the files and folders.
    ad.accountmanager.key.eum=<Existing-Value-1>
ad.accountmanager.key.controller=<Existing-Value-2>
ad.accountmanager.key.mds=<Existing-Value-3>
ad.accountmanager.key.ops=<Existing-Value-4>
ad.accountmanager.key.slm=<Existing-Value-5>
ad.accountmanager.key.jf=<Existing-Value-6>
ad.accountmanager.key.account_service=<Existing-Value-7>
ad.accountmanager.key.admin_service=<Existing-Value-8>
ad.accountmanager.key.service=<Existing-Value-9>

    If you have activated or deactivated any properties, ensure that those properties correctly are updated in the Events Service node. Verify and update the values from the backup folder.

  4. Extract the events-service.zip file that you copied from the temporary instance.
  5. Copy the extracted contents from events-service folder to <APPDYNAMICS-HOME> folder.

Update the Events Service Node

  1. Update the properties file as follows:
    ad.dw.http.host=<ES_Instance-x_ip>
ad.dw.http.adminHost=<ES_Instance-x_ip>
ad.es.node.network.bind.host=<ES_Instance-x_ip>
ad.es.node.unicast.hosts=<ES_Instance-1_ip>:9300,<ES_Instance-2_ip>:9300,<ES_Instance-3_ip>:9300
ad.es.cluster.initial_master_nodes=<ES_Instance-1_ip>,<ES_Instance-2_ip>,<ES_Instance-3_ip>
ad.es.cluster.http.hosts=<ES_Instance-1_ip>:9200,<ES_Instance-2_ip>:9200,<ES_Instance-3_ip>:9200
ad.es.node.network.publish.host=<ES_Instance-x_ip>
ad.es.event.index.replicas=1
ad.es.metadata.replicas=1
ad.es.metadata.entities.replicas=1
  2. Update the keys to match with other nodes.
  3. Update system environment variables or you can use command line to set variables for the specific environment.
    • JAVA_HOME: <APPDYNAMICS-HOME>\events-service\processor\jre
    • ES_JAVA_HOME: <APPDYNAMICS-HOME>\events-service\processor\jre
  4. Update PATH environment variable to use <AppDynamicsHome>\events-service\processor\jre\bin of Events Service.
    Note: Ensure to use the new command window so that it fetches the updated values to start the Events Service.
  5. Start the Events Service node using the following command:
    cd <APPDYNAMICS-HOME>/events-service/processor/bin
events-service.exe start -p ../conf/events-service-api-store.properties
  6. Check the node whether it has rejoined the cluster using the following command:
    curl localhost:9200/_cat/nodes

    If the output is yes, then the upgrade is successful.

  7. Repeat the following steps on other nodes in the Events Service cluster.
Note: Use the events-service.exe command to start or stop Events Service instead of Enterprise Console.