1. Describe your incident:
We are unable to add a second data node to our graylog cluster. We see the node on the web GUI, but it says unavailable. The logs from the new data node
[2025-04-02T09:58:20,654][WARN ][o.o.c.c.ClusterFormationFailureHelper] [graylogdata003] cluster-manager not discovered or elected yet, an election requires two nodes with ids [xxxxxx], have discovered [{graylogdata003}{ xxxxxx }{ xxxxxx }{ graylogdata003}{127.0.1.1:9300}{dimr}{shard_indexing_pressure_enabled=true}] which is not a quorum; discovery will continue using [127.0.0.1:9300, [::1]:9300] from hosts providers and [{graylogdata003}{ xxxxxx }{ xxxxxx }{graylogdata003}{127.0.1.1:9300}{dimr}{shard_indexing_pressure_enabled=true}] from last-known cluster state; node term 10, last-accepted version 0 in term 0
2. Describe your environment:
-
OS Information: vSphere 8 environment. Ubuntu 22 on all VMs.
-
Package Version: 6.1
3. What steps have you already taken to try and solve the problem?
I followed this guide to set up the second node.
I also tried to update the opensearch.yml file and uncommented these sections to add the data nodes in the cluster by IP, using 127.0.0.1 for the new node, and the IP address of the already-established node.
`discovery.seed_hosts: - “127.0.0.1:9300” - “192.168.1.2:9300”
4. How can the community help?
Has anyone encountered this sort of issue? I am not 100% sure if the error I posted is even related to the fact that the new node isn’t available, and was hoping for some guidance. Thanks.
Helpful Posting Tips: Tips for Posting Questions that Get Answers [Hold down CTRL and link on link to open tips documents in a separate tab]