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

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

That's super old, it's no longer supported. Please upgrade :slight_smile:

It's also likely to be a JVM issue.

When did you make the change?

@warkolm It's very old I know that :sweat_smile: .

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?

If you want to delete all your data as well :slight_smile:

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

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

1 Like