Health check failed

Elastic Stack Elasticsearch
1

Hi Team

I install elasticsearch 7.2 and only one node, after installed, when I check with curl localhost:9200, it's seem working and return information such version, cluster_name etc, but when i check the health with localhost:9200/_cat/health

it's show me the error "{"error":{"root_cause":[{"type":"master_not_discovered_exception","reason":null}],"type":"master_not_discovered_exception","reason":null},"status":503}"

is there anything configuration incorrect ?

Thanks
Wayne

2

Can you share your config?

3 
#
#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: 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: ["127.0.0.1", "[::1]"]
#
# Bootstrap the cluster using an initial set of master-eligible nodes:
#
#cluster.initial_master_nodes: ["node-1", "node-2"]
#
# 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:
#
#action.destructive_requires_name: true
bootstrap.memory_lock: false
bootstrap.system_call_filter: false
#xpack.security.enabled: true
4

@warkolm Thanks your response, above is the full configuration

Thanks
Wayne

5

this issue fixed, thanks for help

6

Please share the solution in the thread, it might help someone in future :slight_smile:

7

Resolved this issue by enable below setting

node.name: node-1
discovery.seed_hosts: ["node-1"]
cluster.initial_master_nodes: ["node-1"]

1 Like
8

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