A tribe node is built into a usual Node, so there is no special tribe node class. If you pass parameter like "tribe.t1.cluster.name" etc. to the Node settings, a tribe service class is used and performs all the necessary work in the background. Basically the API stays the same but certain features will throw errors. In fact, the tribe mode opens one or more internal nodes that attach to different clusters, like specified. By listening to the cluster states, they can be merged.
Because the client API does not change compared to a usual Java Node client, I think Kibana can make use of tribe mode right out of the box (but bare with me I am no Kibana expert). Jörg -- 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 [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/CAKdsXoEGg1YuS8Lgom_XdLCx%3Dk%2BvscQcBGGMWdmUpwN%2BJye_zA%40mail.gmail.com. For more options, visit https://groups.google.com/groups/opt_out.
