Hi there!
I'm trying to install ES cluster on GCP VMs.
Only for test purposes, I'm trying to see if discovery works with 2 machines, and ES 7.5.1
My elasticsearch.yml is:
# ======================== 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: test-cluster
#
# ------------------------------------ Node ------------------------------------
#
# Use a descriptive name for the node:
#
node.name: es-test-1n80
#
# Add custom attributes to the node:
#
#node.attr.rack: r1
#
# ----------------------------------- 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.memory_lock: 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: 192.168.0.1
network.publish_host: _site_
network.bind_host: 0.0.0.0
# 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: ["es-test-1n80", "es-test-8v1l"]
#
# Bootstrap the cluster using an initial set of master-eligible nodes:
#
cluster.initial_master_nodes: ["es-test-1n80", "es-test-8v1l"]
discovery.zen.minimum_master_nodes: 1
#
# For more information, consult the discovery and cluster formation module documentation.
#
# ---------------------------------- Gateway -----------------------------------
#
# Block initial recovery after a full cluster restart until N nodes are started:
#
#gateway.recover_after_nodes: 3
#
# For more information, consult the gateway module documentation.
#
# ---------------------------------- Various -----------------------------------
#
# Require explicit names when deleting indices:
#
And I'm getting the following error -
[2020-01-03T14:14:57,844][WARN ][o.e.c.c.ClusterFormationFailureHelper] [es-test-1n80] master not discovered yet, this node has not previously joined a bootstrapped (v7+) cluster, and this node must discover master-eligible nodes [es-test-1n80, es-test-8v1l] to bootstrap a cluster: have discovered [{es-test-1n80}{4jRPBwTDRo2GPesCXfFb6g}{RaTfc5-oQ3igb45stYRxKA}{10.xxx.x.76}{10.xxx.x.76:9300}{dilm}{ml.machine_memory=15774404608, xpack.installed=true, ml.max_open_jobs=20}]; discovery will continue using [10.xxx.x.77:9300] from hosts providers and [{es-test-1n80}{4jRPBwTDRo2GPesCXfFb6g}{RaTfc5-oQ3igb45stYRxKA}{10.xxx.x.76}{10.xxx.x.76:9300}{dilm}{ml.machine_memory=15774404608, xpack.installed=true, ml.max_open_jobs=20}] from last-known cluster state; node term 0, last-accepted version 0 in term 0
The 9200 is opened in GCP Firewall rules.
Could you please advice why it can't discover the master nodes?
Thanks!