Unable to make my cluster state as Green even with more than 1 nodes

Hello Team,

I have two instances in same host,
In one instance data already loaded without any extra node connected to that..

Then after for to create cluster, changes made in Node 1 as:
cluster.name: elasticsearch
node.name: node1
node.master: true
node.data: true
http:port: 9200
tcp.port: 9300
discovery.zen.ping.multicast.enabled: false
discovery.zen.ping.unicast.hosts: [“192.168.1.59:9300”,”192.168.1.59:9301”]

changes made in Node2 elasticsearch.yml file:
cluster.name: elasticsearch
node.name: node2
node.master: true
node.data: true
http:port: 9201
tcp.port: 9301
discovery.zen.ping.multicast.enabled: false
discovery.zen.ping.unicast.hosts: [“192.168.1.59:9300”,”192.168.1.59:9301”]

Then I have started node 1 and the started node 2

when I check for cluster health status as:

GET _cluster/health?pretty=true:

Response:

"cluster_name": "elasticsearch",
"status": "yellow",
"timed_out": false,
"number_of_nodes": 2,
"number_of_data_nodes": 2,
"active_primary_shards": 45,
"active_shards": 45,
"relocating_shards": 0,
"initializing_shards": 0,
"unassigned_shards": 45,
"number_of_pending_tasks": 0

The same response am seeing in 192.168.1.59:9200, 192.168.1.59:9201..

May I know why the cluster is not making its status to green even though it have more than 1 node connected in a host?????

Is there anything in the ES logs that would indicate why ES isn't able to assign shards to the newly added node? Is there ample disk space on that node?

Hi Magnus,

Thanks for your response.
In logs am unable to see anything,, may I know what is ample disk space and why do we need to consider that???
And how to check that ample disk space????

One more to Say that both nodes 192.168.1.59:9200 and 192.168.1.59:9201 are accessable (able to get data from both nodes, which seems like both are communicating)..
But unable to make them Green state...

may I know what is ample disk space and why do we need to consider that???

Elasticsearch will refuse to allocate shards on node with less than 15% free space on the partition that's supposed to contain the ES data. See Disk-based shard allocation | Elasticsearch Guide [8.11] | Elastic.

And how to check that ample disk space????

With the df tool, for example.