Second node of the Search Server cluster does not work
search cancel

Second node of the Search Server cluster does not work

book

Article ID: 264635

calendar_today

Updated On:

Products

CA Service Management - Service Desk Manager CA Service Desk Manager

Issue/Introduction

The second node of the Search Server Cluster is running but is not able to connect to the master node.

Error in ca_es_cluster.log

"failed to join" "this node previously joined a cluster with uuid"

The Elastic Search plugin shows cluster health: red

and does not show the master node:

 

 

Environment

Release : 17.3 and higher

Cause

The node is linked to another cluster or master node

Resolution

1. Stop Search Server service in all nodes

2. Take a backup of C:\Program Files\CA\SC\CASearchServer\elasticsearch-<version>\data folder in the node that is not able to connect to the master node

3. Rename the data folder to something else in the node that is not able to connect to the master node. ie: data_backup

4. Ensure the elasticsearch.yml from all nodes is configured following the instructions in the link below:

Configure Search Server Cluster

5. Start Services in all nodes. The data folder should be re-created in the node with the problem and should be able to connect to the master node if it's configured in the right way. Review the ca_es_cluster.log and/or connect to Elastic Search Chrome plugin to confirm this.