Elasticsearch 7.6 Cluster Configuration

Hi, I am having issue with Elasticsearch 7.6 cluster configuration. Cluser status is RED.
curl -XGET master1:9200/_cat/nodes prints: 10.69.61.201 8 63 0 0.00 0.01 0.05 ilm * master1.ela.soc.xxx
curl -XGET data1:9200/_cat/nodes prints: nothing
data1 node log: join validation on cluster state with a different cluster uuid gb9uQwICTuGyYnjk63m1Jw than local cluster uuid uSFkkdgCQJWduLjbbLgo3w, rejecting
Please advise.

Setup:
3 Master Nodes + 3 Data nodes
elasticsearch.yml

======================== Elasticsearch Configuration =========================

NOTE: Elasticsearch comes with reasonable defaults for most settings.

Before you set out to tweak and tune the configuration, make sure you

understand what are you trying to accomplish and the consequences.

The primary way of configuring a node is via this file. This template lists

the most important settings you may want to configure for a production cluster.

Please consult the documentation for further information on configuration options:

https://www.elastic.co/guide/en/elasticsearch/reference/index.html

---------------------------------- Cluster -----------------------------------

Use a descriptive name for your cluster:

cluster.name: ELA.SOC.XXX

------------------------------------ Node ------------------------------------

Use a descriptive name for the node:

node.name: master1.ela.soc.xxx

Add custom attributes to the node:

node.attr.rack: master1

Define node 1 as master node

node.master: true

node.data: false

----------------------------------- Paths ------------------------------------

Path to directory where to store the data (separate multiple locations by comma):

path.data: /var/lib/elasticsearch

Path to log files:

path.logs: /var/log/elasticsearch

----------------------------------- Memory -----------------------------------

Lock the memory on startup:

#bootstrap.mlockall: true

Make sure that the heap size is set to about half the memory available

on the system and that the owner of the process is allowed to use this

limit.

Elasticsearch performs poorly when the system is swapping the memory.

---------------------------------- Network -----------------------------------

Set the bind address to a specific IP (IPv4 or IPv6):

network.host: 10.69.61.201

Set a custom port for HTTP:

http.port: 9200

For more information, consult the network module documentation.

--------------------------------- Discovery ----------------------------------

Pass an initial list of hosts to perform discovery when this node is started:

The default list of hosts is ["127.0.0.1", "[::1]"]

discovery.seed_hosts: ["10.69.61.201", "10.69.61.202", "10.69.61.203", "10.69.61.211", "10.69.61.212", "10.69.61.213"]

Bootstrap the cluster using an initial set of master-eligible nodes:

cluster.initial_master_nodes: ["10.69.61.201", "10.69.61.202", "10.69.61.203"]

For more information, consult the discovery and cluster formation module documentation.

discovery.zen.minimum_master_nodes: 2

---------------------------------- Gateway -----------------------------------

Block initial recovery after a full cluster restart until N nodes are started:

gateway.expected_nodes: 6
gateway.expected_master_nodes: 3
gateway.expected_data_nodes: 3

gateway.recover_after_nodes: 3

For more information, consult the gateway module documentation.

---------------------------------- Various -----------------------------------

Require explicit names when deleting indices:

action.destructive_requires_name: true

RESOLVED - stop elasticsearch.service and delete data from /var/lib/elasticsearch/* or simply data path.

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.