Atlassian uses cookies to improve your browsing experience, perform analytics and research, and conduct advertising. Accept all cookies to indicate that you agree to our use of cookies on your device. Atlassian cookies and tracking notice, (opens new window)
To be able to work with Zephyr Data Center, you need to install and configure Elasticsearch -- a search and analytics engine -- on a separate node. Depending on the number of concurrent users who will work with the Data Center, you may need to set up one Elasticsearch node or a cluster of nodes (see Recommended Configurations).
If you use an Elasticsearch cluster, there is no need to use an external load balancer, as Elasticsearch used in a cluster has the load balancing capability.
To install Elasticsearch on Windows (on a single node or on cluster nodes):
The number of Elasticsearch nodes you use in a cluster should be odd. That is, the minimum number of nodes you can use in a cluster is 3.
To avoid split-brain, you need to specify an appropriate value for the discovery.zen.minimum_master_nodes parameter. To determine it, follow the rule N/2+1, where N is the number of nodes in the cluster. In a three-node cluster, the parameter should be set to 2 (3/2+1=2 - rounded down to the nearest integer).
1. Specify the following properties in the elasticsearch.yml file on all Elasticsearch nodes:
If you have configured an Elasticsearch cluster, change the number_of_shardsand number_of_replicas values in the Zephyr\tomcat\webapps\flex\WEB-INF\template\zephyr\_settings.json file: "number_of_shards" : 2, "number_of_replicas" : 1
For a single node, leave the default values.
4. Start the service by running the elasticsearch-6.8.1\bin\elasticsearch.bat file.
To install Elasticsearch on Linux (on a single node or on cluster nodes):
The number of Elasticsearch nodes you use in a cluster should be odd. That is, the minimum number of nodes you can use in a cluster is 3.
To avoid split-brain, you need to specify an appropriate value for the discovery.zen.minimum_master_nodes parameter. To determine it, follow the rule N/2+1, where N is the number of nodes in the cluster. In a three-node cluster, the parameter should be set to 2 (3/2+1=2 - rounded down to the nearest integer).
1. Specify the following properties in the elasticsearch.yml file on all Elasticsearch nodes (replace the IPs with your IPs):
discovery.zen.ping.unicast.hosts should list all the IPs and ports used in the cluster.
2. After creating all the nodes, delete the /var/lib/elasticsearch/nodes folder on all the nodes, then restart.
If you have configured an Elasticsearch cluster, change the number_of_shardsand number_of_replicas values in the Zephyr\tomcat\webapps\flex\WEB-INF\template\zephyr\_settings.json file: "number_of_shards" : 2, "number_of_replicas" : 1
For a single node, leave the default values.
4. Start Elasticsearch. The way you start and stop it depends on whether your system uses SysVinit or systemd.
If SysV init is used, you start and stop Elasticsearch by running the service command:
sudo -i service elasticsearch start
sudo -i service elasticsearch stop
If systemd is used, you run the following commands:
sudo systemctl start elasticsearch.service
sudo systemctl stop elasticsearch.service
5. Run the following command to verify Elasticsearch is working properly: