Updating cluster name of existing elasticsearch instance

Asked Feb 23 '20 at 03:03

Active Feb 24 '20 at 15:06

Viewed 363 times

i have updated my cluster name. i have made changes in elasticsearch.yml file, updated clusterName: from 'x' to 'y' and restarted the server. I also made changes to 'renaming the data folder fro x to y' and now i can see the data in elastic head plugin.

i made the same changes in my code for 'cluster name' but i am getting an error NoNodeAvaliable.

for reference - NoNodeAvailableException[None of the configured nodes are available: [{#transport#-1}{...}{127.0.0.1}{127.0.0.1:9300}]]

i have followed everything, restarted my servers. but still noNodeavailable.

any help will be appreciated. thanks

Thanks in advance.

edited Feb 24 '20 at 15:06

asked Feb 23 '20 at 03:03

Lasit Pant

This answer might help: https://stackoverflow.com/a/35144801/4604579 – Val Feb 23 '20 at 06:25
@Val thanks for replying. it did help but i am facing another issue, no node available. i have checked multiple times and the cluster name is the same as on the code and still getting the same, however i can see the updated clustername on elastic head. – Lasit Pant Feb 24 '20 at 13:31
Which version are you running? – Val Feb 24 '20 at 13:31
@Val 2.5.2 is the version. – Lasit Pant Feb 24 '20 at 14:44
Please update your question with all the modifications you just did. – Val Feb 24 '20 at 14:51
@Val updated the same. – Lasit Pant Feb 24 '20 at 15:06
Are you sure you have no typos anywhere? – Val Feb 24 '20 at 15:07
yep , its just i have one server for elastic and another running the code and communicating to the transport layer – Lasit Pant Feb 24 '20 at 15:17
Can you show the logs of the Elasticsearch server when it restarted? – Val Feb 24 '20 at 15:18
nothing much in it. i cannot get you a screen grab though publish address : the IP:9300 recovered 41 indices – Lasit Pant Feb 24 '20 at 15:23
Please share them – Val Feb 24 '20 at 15:24
actually i can't its my prod server (which is inhouse) and i cannot move stuff even with a pd – Lasit Pant Feb 24 '20 at 15:28
Does your client server have the correct host/IP address to connect to your Elasticsearch server? Is the client code also hosted on the same server as Elasticsearch? (since I see `127.0.0.1:9300` in your log) – Val Feb 24 '20 at 15:30
@Val yep its all correct – Lasit Pant Feb 24 '20 at 16:21
@Val thanks man really appreciate your help. i made a couple of more config changes to elasticsearch.yml - transport.host: xxxxxx (IP) and transport.ip:9300 and did a restart and probably went for lunch came and the boom it worked. Thanks again. !!! – Lasit Pant Feb 24 '20 at 19:55
Awesome, glad you figured it all out. – Val Feb 24 '20 at 21:04

Updating cluster name of existing elasticsearch instance

0 Answers0