I've just implemented your cluster system and every node works as to be in cloud (load balancing). But if Master node goes down i cannot retrive any info from kibana dashboards. As per your tutorial you said "After the cluster has started, and all nodes are connected, any of the nodes can be chosen as master node if the current master node in use goes offline for any period of time". In this case how can i promote the other node to Master to avoid failover system of current Mater-node?
![[Elasticsearch] Как собрать кластер Elasticsearch. Какие есть роли у нод Elasticsearch.](http://i.ytimg.com/vi/-e0M9X6uD_4/mqdefault.jpg)
Just the thing I was looking for. Searched lot of videos before this. This one is underrated. Good stuff thanks
very nice explanation... the most interesting part was deleting cache that in some cases might cause the problem
well done & great explanation
i like the hint given about deleting the node folder and getting rid of the old cach
because i got the same issue
straight to the point. nice tutorial.
Ty Sir :) this video was really interesting and helpful
I've just implemented your cluster system and every node works as to be in cloud (load balancing). But if Master node goes down i cannot retrive any info from kibana dashboards. As per your tutorial you said "After the cluster has started, and all nodes are connected, any of the nodes can be chosen as master node if the current master node in use goes offline for any period of time". In this case how can i promote the other node to Master to avoid failover system of current Mater-node?
Thank you
hi, thanks for the video. I have a question. Is it possible to install another elasticsearch instance under the same ubuntu server?
"cluster_name" : "ASIEM",
"status" : "red",
"timed_out" : false,
ststus is red what should i do
find and delete any RED index if you don't need it. It will resolved the cluster health
Great thanks!