I am new to ELK and I am still using a dev environment with real data to understand how the pipeline works.
Recently I had nodes networking between them that were part of a 4 node cluster: 1 master node, no data and 3 data-only nodes. These were working fine up to the point that they lost connectivity between themselves. I am using a unicast cluster setup as multicast was not working on my OpenStack cluster (a question for another future post). When I rebooted the nodes and tried to bring the master back up it tried to join the previous master instance. Clearly there is information cached about the previous running instance that needs to be flushed. As this is a dev environment, I copied the config file and blew away the elastic search directory, copied the config back and tried to restart elasticsearch. Curiously it is still trying to join the old master, even though no other processes are running. Obviously this cached data lives somewhere else on the system and I have yet to find it. Perhaps someone can point me in the right direction here. -- You received this message because you are subscribed to the Google Groups "elasticsearch" group. To unsubscribe from this group and stop receiving emails from it, send an email to elasticsearch+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/90187018-dde9-447d-b211-d806fd46cec8%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
