# Node IPs in the cluster does not changed when the host/system IPs already changed

**URL:** <https://discuss.elastic.co/t/node-ips-in-the-cluster-does-not-changed-when-the-host-system-ips-already-changed/228949>\
**Category:** Elasticsearch\
**Created:** [April 21, 2020, 3:30am UTC](https://discuss.elastic.co/t/node-ips-in-the-cluster-does-not-changed-when-the-host-system-ips-already-changed/228949 "2020-04-21T03:30:27Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![worapojc](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/worapojc/32/42782_2.png) [@worapojc](https://discuss.elastic.co/u/worapojc)\
**Post date:** [April 21, 2020, 3:30am UTC](https://discuss.elastic.co/t/node-ips-in-the-cluster-does-not-changed-when-the-host-system-ips-already-changed/228949/1 "2020-04-21T03:30:27Z")

</div>

Hello Elasticsearch team,

I'm using Elasticsearch 1.7, here is the \_cat/nodes response.

> curl -s localhost:9200/\_cat/nodes  
> data\_node\_1 10.255.70.31 14 54 1.98 d - data\_node\_1.instance.3  
> master\_node\_1 159.42.11.42 2 14 0.02 - m master\_node\_1.instance.1  
> data\_node\_2 10.255.70.32 43 54 4.71 d - data\_node\_2.instance.1  
> data\_node\_3 10.255.70.33 69 53 2.04 d - data\_node\_3.instance.2  
> query\_node\_1 159.42.11.48 1 22 0.07 - - query\_node\_1.instance.1  
> data\_node\_1 10.255.70.31 60 54 1.98 d - data\_node\_1.instance.1  
> data\_node\_3 10.255.70.33 35 53 2.04 d - data\_node\_3.instance.3  
> data\_node\_3 10.255.70.33 65 53 2.04 d - data\_node\_3.instance.4  
> data\_node\_3 10.255.70.33 55 53 2.04 d - data\_node\_3.instance.1  
> data\_node\_2 10.255.70.32 28 54 4.71 d - data\_node\_2.instance.4  
> data\_node\_1 10.255.70.31 40 54 1.98 d - data\_node\_1.instance.2  
> data\_node\_2 10.255.70.32 45 54 4.71 d - data\_node\_2.instance.2  
> query\_node\_2 159.42.11.47 1 22 0.05 - - query\_node\_2.instance.1  
> master\_node\_2 159.42.11.43 0 14 0.14 - \* master\_node\_2.instance.1  
> data\_node\_1 10.255.70.31 68 54 1.98 d - data\_node\_1.instance.4  
> data\_node\_2 10.255.70.32 25 54 4.77 d - data\_node\_2.instance.3  
> master\_node\_3 159.42.11.44 2 14 0.01 - m master\_node\_3.instance.1

However, the data node IPs have been changed from 10.255.x.x to 159.42.x.x.  
I did full rolling restart but the IPs from \_cat/nodes have not been changed.

I guess it might have a cache at the Elasticsearch level.  
How do I fix this issue?

Regards,  
Worapoj

---

<div class="post-metadata">

**Author:** ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)\
**Post date:** [April 21, 2020, 6:19am UTC](https://discuss.elastic.co/t/node-ips-in-the-cluster-does-not-changed-when-the-host-system-ips-already-changed/228949/2 "2020-04-21T06:19:01Z")

</div>

> [@worapojc](#):
>
> I'm using Elasticsearch 1.7

That's super old, it's [no longer supported](https://www.elastic.co/support/eol). Please upgrade 🙂

> [@worapojc](#):
>
> I guess it might have a cache at the Elasticsearch level.

It's also likely to be a JVM issue.

When did you make the change?

---

<div class="post-metadata">

**Author:** ![worapojc](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/worapojc/32/42782_2.png) [@worapojc](https://discuss.elastic.co/u/worapojc)\
**Post date:** [April 21, 2020, 7:29am UTC](https://discuss.elastic.co/t/node-ips-in-the-cluster-does-not-changed-when-the-host-system-ips-already-changed/228949/3 "2020-04-21T07:29:11Z")

</div>

@warkolm It's very old I know that 😅 .

I tried to stop all services in all nodes, and start it again. The cluster is working fine but it still remember the old IP addresses.  
Should I clear data in **path.data** fields of the configuration file in all nodes?

---

<div class="post-metadata">

**Author:** ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)\
**Post date:** [April 21, 2020, 8:33pm UTC](https://discuss.elastic.co/t/node-ips-in-the-cluster-does-not-changed-when-the-host-system-ips-already-changed/228949/4 "2020-04-21T20:33:56Z")

</div>

> [@worapojc](#):
>
> Should I clear data in **path.data** fields of the configuration file in all nodes?

If you want to delete all your data as well 🙂

I'm not sure how to clear the JVM of this data sorry.

---

<div class="post-metadata">

**Author:** ![worapojc](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/worapojc/32/42782_2.png) [@worapojc](https://discuss.elastic.co/u/worapojc)\
**Post date:** [May 7, 2020, 11:20am UTC](https://discuss.elastic.co/t/node-ips-in-the-cluster-does-not-changed-when-the-host-system-ips-already-changed/228949/5 "2020-05-07T11:20:47Z")

</div>

Just updated the ticket. My bad, the IP was fixed /etc/hosts. ☹

---

<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:** [June 4, 2020, 11:20am UTC](https://discuss.elastic.co/t/node-ips-in-the-cluster-does-not-changed-when-the-host-system-ips-already-changed/228949/6 "2020-06-04T11:20:53Z")

</div>

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