PDFs

Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  1. Follow the steps for configuring a single node cluster in the 1-node installation above. Additionally, configure the following settings in the  conf\events-store-api-store.properties  file:

    1. Change the value of the ad.es.node.minimum_master_nodes property to 2:

      No Format
      ad.es.node.minimum_master_nodes=2

      The setting specifies the minimum number of master-eligible instances that must be available in order to elect a new master. Since an Events Service cluster has three master nodes, this value should be two for a cluster.

    2. Set the value of ad.es.event.index.shards to the number of nodes, in this case three:

      No Format
      ad.es.event.index.shards=3

      You do not need to change this value if it is already higher than the number of nodes.

    3. Set the replication factor to 1 by changing the ad.es.event.index.replicas and ad.es.metadata.replicas properties, as follows:

      No Format
      ad.es.event.index.replicas=1
      ad.es.event.index.hotLifespanDays=10
      ad.es.event.index.warmLifespanDays=0
      
      ad.es.metadata.replicas=1
    4. For the unicast hosts property, add the hostname or IP address, along with the port 9300, for each node in the cluster:

      No Format
      ad.es.node.unicast.hosts=node1.example.com:9300,node2.example.com:9300,node3.example.com:9300
    5. Change the publish host to the IP address or hostname of this machine. For example:

      No Format
      ad.es.node.network.publish.host=node2.example.com
    6. Allocate heap space for the process. To set it to 8 GB, for 

      No Format
      ad.jvm.options.name=events-service.vmoptions
      ad.jvm.heap.min=8g
      ad.jvm.heap.max=8g

      Set the heap size to half of the size of available RAM on the system, up to a maximum of 31 GB. For the setting value, g indicates gigabyte (GB), and m indicates megabyte (MB). 

    7. Save and close the file.
  2. Install the Events Service as a Windows service:  

    No Format
    bin\events-service.exe service-install -p conf\events-service-api-store.properties  --auto-start

    The optional auto-start flag causes the Events Service to be installed as an automatically started service. If you do not include the flag, the Events Service is installed as a manually started service. An additional option, ‑‑log-verbose, increases the verbosity of installation and operation logging, which is useful for troubleshooting.

  3. Enter the following command to find the service name for the Events Service:

    No Format
    bin\events-service.exe service-list
  4. Pass the service name returned by the service-list command as the -s parameter argument in the following command: 

    No Format
    bin\events-service.exe service-start -s "<Name from service-list>" 

    Be sure to enclose the name in double quotes. 

  5. Check the health of the new node using the following command. At least two nodes must be running before you run the command. 

    No Format
    bin\events-service.exe check-health -hp localhost:9081

    For the port, pass the administration port for the Events Service, 9081 by default. Verify that "Healthy" appears as the service status, indicating that the process is operating normally:

    No Format
    [appduser@controller-one events-service]$ bin/events-service.exe check-health -hp 192.168.33.22:9081
    [2015-12-09T18:30:45,342-08:00] HV000001: Hibernate Validator 5.0.2.Final
    [2015-12-09T18:30:45,956-08:00] Individual statuses below:
    [2015-12-09T18:30:45,956-08:00] [192.168.33.22:9081] status is [200 OK]
    [2015-12-09T18:30:45,956-08:00] Overall status Healthy
    ...
  6. Configure a load balancer to distribute traffic to the Events Service cluster, as described in Load Balance Events Service Traffic

  7. Connect the Controller and other clients—Analytics Agent, EUM Server, or Database Monitoring agents—to the Events Service, as described in Connect to the Events Service.  

...

  1. For each cluster nodes beyond the initial three master nodes, open the conf\events-service-api-store.properties for editing and make these configuration changes:

    1. Set the ad.es.node.master value to false: 

      No Format
      ad.es.node.master=false
    2. Set the ad.es.node.minimum_master_nodes value to 2. 

      No Format
      ad.es.node.minimum_master_nodes=2
    3. Set the value of ad.es.event.index.shards to the number of nodes in the cluster. You do not need to change this value if it is already higher than the number of nodes.

      No Format
      ad.es.event.index.shards=<number_of_nodes>

       You do not need to change this value if it is already higher than the number of nodes.

    4. For the unicast hosts property, add the hostnames or IP addresses of all nodes in the cluster, including the node you are adding. For each node specify the ports on which the nodes communicate, 9300-9400. For example:

      No Format
      ad.es.node.unicast.hosts=node1.example.com[9300-9400],node2.example.com[9300-9400],node3.example.com[9300-9400],node4.example.com[9300-9400]

      You do not need to reconfigure the unicast hosts settings for existing cluster members, as the new node can join the cluster dynamically. 

    5. Change the publish host to the IP address or hostname of this machine. For example:

      No Format
      ad.es.node.network.publish.host=node4.example.com
    6. Disable health checking:

      No Format
      ad.es.health.tool.enabled=false

      Health checking is intended for the first three nodes in the cluster only. 

    7. While editing the events-store-api-store.properties file, scroll to the end of the file and verify the minimum and maximum settings for Events Service process heap allocation.

      No Format
      ad.jvm.heap.min=8g
      ad.jvm.heap.max=8g
    8. Save and close the file.  

  2. Install the Events Service as a Windows service:  

    No Format
    bin\events-service.exe service-install -p conf\events-service-api-store.properties --auto-start 

    The optional auto-start flag causes the Events Service to be installed as an automatically started service. If you do not include the flag, the Events Service is installed as a manually started service. An additional option, ‑‑log-verbose, increases the verbosity of installation and operation logging, which is useful for troubleshooting.

  3. Enter the following command to find the service name for the Events Service:

    No Format
    bin\events-service.exe service-list
  4. Pass the service name returned by the service-list command as the -s parameter argument in the following command: 

    No Format
    bin\events-service.exe service-start -s "<Name from service-list>"  
  5. Check the health of the new node:

    No Format
    bin\events-service.exe check-health -hp localhost:9081

    Note:  At least two nodes must be running before you run the command.

    For the port, pass the administration port for the Events Service, 9081 by default. Verify that "Healthy" appears as the service status, indicating that the process is operating normally:

    No Format
    [appduser@controller-one events-service]$ bin/events-service.bin check-health -hp 192.168.33.22:9081
    [2015-12-09T18:30:45,342-08:00] HV000001: Hibernate Validator 5.0.2.Final
    [2015-12-09T18:30:45,956-08:00] Individual statuses below:
    [2015-12-09T18:30:45,956-08:00] [192.168.33.22:9081] status is [200 OK]
    [2015-12-09T18:30:45,956-08:00] Overall status Healthy
    ...
  6. Modify your load balancer rules to include the new cluster node. For more information, see Load Balance Events Service Traffic.

...