I'm setting up a multi-node elastic cluster with 2 kibana servers. Each of the kibana clusters is on a separate host, each with it's own Coordinating node.
The first kibana/elastic setup is working fine, and the second coordinating node has joined the elastic cluster without issue as well.
The problem that I'm running into is that the second instance of Kibana doesn't see any of the visualizations or dashboards that the other node has configured. Having both Kibana nodes have the same information is pretty important to the business, but I don't see how to sync those -- I was under the impression that all of that went into the '.kibana' index in ElasticSearch -- but that doesn't appear to be the case.
Your assumption about the .kibana index being shared in your scenario is correct.
Are there any errors when you load up the 2nd Kibana, either on the server-side or in the browser? In the browser, you might have to look in your browser's developer console.
Also, what happens if you create a saved visualization in your 2nd Kibana? Does it show up in the first one?
Finally, could you call the GET / Elasticsearch API on each of the two coordinating nodes (e.g. GET 10.0.0.2:9200/ and GET 10.0.0.3:9200/) and paste their results here?
Upon returning to the first Kibana node after posting this, it's dashboards and visualizations were gone as well.
It's almost like installing and starting the second kibana node cleared the .kibana index on the backend(s) - or I somehow suffered data-loss from other means (which is entirely possible given that I was bringing up and down the data nodes throughout the day as I am concurrently working on standardizing how I did the installs).
Apache, Apache Lucene, Apache Hadoop, Hadoop, HDFS and the yellow elephant
logo are trademarks of the
Apache Software Foundation
in the United States and/or other countries.