Tribe Node (global def : port 9200, t1 : port 9201, t2 : port 9202)
Uniform Node * 3
Cluster2
Uniform Node * 3
t1 is for Cluster 1 and t2 is for Cluster 2.
My question is, can elasticsearch.url and elasticsearch.tribe.url be the same url ? In other words, can tribe node (global definition, port 9200) be coordinating node?
I read document but bit anxious so I appreciate if I can get help with my question.
Prior to the 5.x releases we used to suggest a work-around for Kibana with tribe nodes to temporarily point Kibana at the cluster where you want the .kibana index and let it do that. Then change Kibana to point to a tribe node from that point onward. But I don't think that works in 5.x releases (the first part would work, but not the second).
I tested out and confirmed that preparing coordinator node and tribe node is bit too much. It would be better if access to elasticsearch cluster is slimmed into one endpoint.
You could post a request about that on the Elasticsearch forum. They might have something else to suggest or they might create an enhancement request in https://github.com/elastic/elasticsearch
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.