I just have a few questions about the mechanics of a tribe node.
I have set up two clusters, and a tribe node configured to connect to the two of them. First, how can I verify that it is successfully connected. I can run curl commands, but the health check and cluster state checks return only data for the single node (as I believe they were supposed to according to the tribe node documentation). What is a good check to verify connection.
Secondly, I am trying to set up a kibana instance to talk to this node, so that it can search across clusters, and I am getting the errors:
log [20:27:47.739] [info][status][plugin:elasticsearch] Status changed from yellow to yellow - No existing Kibana index found
log [20:28:17.757] [error][status][plugin:elasticsearch] Status changed from yellow to red - Unable to create Kibana index ".kibana"
log [20:28:25.286] [info][status][plugin:elasticsearch] Status changed from red to yellow - No existing Kibana index found
log [20:28:55.293] [error][status][plugin:elasticsearch] Status changed from yellow to red - Unable to create Kibana index ".kibana"
log [20:29:02.833] [info][status][plugin:elasticsearch] Status changed from red to yellow - No existing Kibana index found
log [20:29:32.837] [error][status][plugin:elasticsearch] Status changed from yellow to red - Unable to create Kibana index ".kibana"
log [20:29:40.362] [info][status][plugin:elasticsearch] Status changed from red to yellow - No existing Kibana index found
log [20:30:10.369] [error][status][plugin:elasticsearch] Status changed from yellow to red - Unable to create Kibana index ".kibana"
I assume this is because this is a new kibana node, and it typically creates an index for itself on the cluster to store data in. What is the logical home location for this index if it is connecting to a tribe node?? Should the tribe node be node.data: true?? What if I would like to have a kibana node that queries the tribe node for cross-cluster queries, but also would like to have individual kibana nodes connected to each cluster. Is there a way to configure this?? I can see how it could be a problem because the .kibana index would then exist on multiple clusters, which it appears tribe nodes do not handle well.
Lastly, the documentation states that The tribe node will create a node client to connect each cluster using unicast discovery by default.
Does this mean, that if I run a cluster health check on one of the clusters before and after i turn on the tribe node that it should actually show another node added to the cluster??
Thank you!!!