# "node.name" value not being applied

**URL:** <https://discuss.elastic.co/t/node-name-value-not-being-applied/204367>\
**Category:** Elasticsearch\
**Created:** [October 20, 2019, 4:55pm UTC](https://discuss.elastic.co/t/node-name-value-not-being-applied/204367 "2019-10-20T16:55:14Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![mcohen](https://avatars.discourse-cdn.com/v4/letter/m/ad7895/32.png) [@mcohen](https://discuss.elastic.co/u/mcohen)\
**Post date:** [October 20, 2019, 4:55pm UTC](https://discuss.elastic.co/t/node-name-value-not-being-applied/204367/1 "2019-10-20T16:55:14Z")

</div>

I'm testing with an internal cluster, 3 nodes on the same VM.  
Env: Ubuntu 18.04.3 LTS, elasticsearch-7.3.2-amd64.deb (Debian)

To simulate multiple nodes, I've replicated the `/etc/elasticsearch` directory, results are as follows:  
/etc/elasticsearch  
/etc/elasticsearch-node-2  
/etc/elasticsearch-node-3

Here's the config for one of the elasticsearch.yml files (ie: `/etc/elasticsearch/elasticsearch.yml`):

```
cluster.name: new-tokyo
node.name: akira
path.data: /opt/elasticsearch-data
path.logs: /opt/elasticsearch-logs
network.host: 0.0.0.0
http.port: 9200
cluster.initial_master_nodes: ["akira", "tetsuo", "kaneda"]
node.max_local_storage_nodes: 3

```

The only difference between the 3 `elasticsearch.yml` files is:

- `node.name` value (akira, tetsuo, kaneda)
- `http.port` value (9200, 9201, 9202)

`jvm.options` is identical for all three nodes. (512m)

If I start the nodes and pass the value from the command line (ie: `ES_PATH_CONF=/etc/elasticsearch-node-2/`) then the node names are unique.

If I setup and start elasticsearch as a service (ie: `systemctl start elasticsearch.service`), the node names are all the same, `akira`.

Whats particularly confusing is that I can change other values, such as `http.port` and the change is reflected (once restarted). Is this data cached somewhere? I've tried trashing the data folder (stock location `/var/lib/elasticsearch/nodes` and my custom location `/opt/elasticsearch-data/nodes/`), to no avail, and have literally spent days trying to figure this out, and have tried with 7.3, and 7.4. Any assistance is appreciated, thanks.

---

<div class="post-metadata">

**Author:** ![mcohen](https://avatars.discourse-cdn.com/v4/letter/m/ad7895/32.png) [@mcohen](https://discuss.elastic.co/u/mcohen)\
**Post date:** [October 20, 2019, 5:08pm UTC](https://discuss.elastic.co/t/node-name-value-not-being-applied/204367/2 "2019-10-20T17:08:22Z")

</div>

Here's an example of the relevant errors I'm seeing in the logs, "MasterNotDiscoveredException", etc...

`[akira] bootstrapping cancelled java.lang.IllegalStateException: requirement [akira] matches multiple nodes:`

and

`this node must discover master-eligible nodes [akira, tetsuo, kaneda] to bootstrap a cluster: have discovered [{akira}`

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [November 17, 2019, 5:08pm UTC](https://discuss.elastic.co/t/node-name-value-not-being-applied/204367/3 "2019-11-17T17:08:23Z")

</div>

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