Two nodes, set on the same machine, can't see each other - Dev purposes

Elastic Stack Elasticsearch
1

Hi,
We have a problem in our organization. We are trying to add second node, to existing cluster, on the same machine. I know it's not a good solution, but we only do it for development purposes. The version that we are using is: 7.8
Our problem is that we are actually able to run two nodes on the same machine, but they don't detect each other - that is, when creating a node, each is created with totally new cluster ID, and they are not interconnected with each other.
When it comes to the configuration file, we only use the basic settings, as two nodes are running on the same machine, and there is no need to set up advanced stuff.
The parameters that we changed, is the node name, network host, we set up paths, node.max_local_storage_nodes: 2. Cluster name is the same for both nodes, and http ports are established automatically.
Is there any step that we skip that causes the two nodes do not find each other? Do you have any ideas? Thanks in advance!

Cluster

cluster.name: uipath-test
cluster.initial_master_nodes: 2

``````````````` Node ````````````````

node.name: node-2
node.max_local_storage_nodes: 2

````````````````Paths ``````````````````

path.data: D:\Elasticsearch\data
path.logs: D:\Elasticsearch\logs

#``````````````````Network `````````````````
network.host: [..........]
http.port: 9201
#``````````````Discovery ````````````````
transport.tcp.port: 9301

2

This parameter is deprecated, don't use it, it's trappy because it requires the nodes to race against each other when starting up. Instead give each node a different value for path.data.

You have not set cluster.initial_master_nodes correctly, it should be a list of the node names:

cluster.initial_master_nodes: ["node-1", "node-2"]

You'll need to fix this and delete the contents of D:\Elasticsearch\data to reset everything.

4

I think there'll be more helpful information in the logs.

6

I think this is not the only message in the logs. This alone doesn't tell us much.

9

Yes, this is slightly more useful:

As it says, it needs to discover nodes node-1 and node-2 but it's only discovered node-1. You've edited this message to remove details like the discovery config which is often the source of this problem -- you're making it really quite difficult to offer useful help!