# Tribe nodes **URL:** \ **Category:** Elasticsearch\ **Created:** [January 16, 2014, 1:58pm UTC](https://discuss.elastic.co/t/tribe-nodes/15271 "2014-01-16T13:58:45Z")\ **Posts on this page:** 10\ **Page:** 1
**Author:** ![Mihai\_Oprea](https://avatars.discourse-cdn.com/v4/letter/m/57b2e6/32.png) [@Mihai\_Oprea](https://discuss.elastic.co/u/Mihai_Oprea)\ **Post date:** [January 16, 2014, 1:58pm UTC](https://discuss.elastic.co/t/tribe-nodes/15271/1 "2014-01-16T13:58:45Z")
Hi all, I took a look at some of the changes that Elasticsearch RC1 brings and I was wondering what use cases you found for tribe nodes. What are the benefits of using a tribe node over multiple clusters versus just having more indexes in the same cluster. Best, Mihai -- 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 [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com). To view this discussion on the web visit [https://groups.google.com/d/msgid/elasticsearch/256196bd-a160-4bc1-849d-4e0da73ad9f4%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/256196bd-a160-4bc1-849d-4e0da73ad9f4%40googlegroups.com). For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out). ---
**Author:** ![jprante](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/jprante/32/44941_2.png) [@jprante](https://discuss.elastic.co/u/jprante)\ **Post date:** [January 16, 2014, 2:40pm UTC](https://discuss.elastic.co/t/tribe-nodes/15271/2 "2014-01-16T14:40:10Z")
The tribe node can be useful if your organization is maintaining several clusters (for whatever reasons) but you want to search all of them. Also useful could be transferring data between clusters by a single client in a single step. Reasons can be organizational, or geographical, or logical. Maybe you have grown several clusters that you do not want to merge, or several data centers, or you want to compare data in a staging area with current production cluster, so you could span internal and external visible clusters simply by executing a tribe node search. 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 [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com). To view this discussion on the web visit [https://groups.google.com/d/msgid/elasticsearch/CAKdsXoHauncAkaNPRX6i18fPTf5gZihm-HTMAPZQxdTwS1m\_Pw%40mail.gmail.com](https://groups.google.com/d/msgid/elasticsearch/CAKdsXoHauncAkaNPRX6i18fPTf5gZihm-HTMAPZQxdTwS1m_Pw%40mail.gmail.com). For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out). ---
**Author:** ![dkjhanitt](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/dkjhanitt/32/1575_2.png) [@dkjhanitt](https://discuss.elastic.co/u/dkjhanitt)\ **Post date:** [January 16, 2014, 7:45pm UTC](https://discuss.elastic.co/t/tribe-nodes/15271/3 "2014-01-16T19:45:57Z")
HI Jorg, I posted a question for the same issue yesterday and I was referenced to look at > **[Elasticsearch Platform — Find real-time answers at scale](https://www.elastic.co)** > > Power insights and outcomes with the Elasticsearch Platform and AI. See into your data and find answers that matter with enterprise solutions designed to help you build, observe, and protect. Try Elasticsearch free today. . My question is lets say I want to query across multiple cluster using Kibana, then do I need to put tribe node details in elasticsearch ? Also, is it a new type of node on top of Master, client, data ? Thanks, Deepak On Thursday, January 16, 2014 6:40:10 AM UTC-8, Jörg Prante wrote: > The tribe node can be useful if your organization is maintaining several > clusters (for whatever reasons) but you want to search all of them. > > Also useful could be transferring data between clusters by a single client > in a single step. > > Reasons can be organizational, or geographical, or logical. Maybe you have > grown several clusters that you do not want to merge, or several data > centers, or you want to compare data in a staging area with current > production cluster, so you could span internal and external visible > clusters simply by executing a tribe node search. > > 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 [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com). To view this discussion on the web visit [https://groups.google.com/d/msgid/elasticsearch/f60c5251-f34e-4950-a808-836ab5980400%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/f60c5251-f34e-4950-a808-836ab5980400%40googlegroups.com). For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out). ---
**Author:** ![jprante](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/jprante/32/44941_2.png) [@jprante](https://discuss.elastic.co/u/jprante)\ **Post date:** [January 16, 2014, 9:48pm UTC](https://discuss.elastic.co/t/tribe-nodes/15271/4 "2014-01-16T21:48:53Z")
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 [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com). To view this discussion on the web visit [https://groups.google.com/d/msgid/elasticsearch/CAKdsXoEGg1YuS8Lgom\_XdLCx%3Dk%2BvscQcBGGMWdmUpwN%2BJye\_zA%40mail.gmail.com](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](https://groups.google.com/groups/opt_out). ---
**Author:** ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)\ **Post date:** [January 16, 2014, 9:52pm UTC](https://discuss.elastic.co/t/tribe-nodes/15271/5 "2014-01-16T21:52:30Z")
Does anyone know if a tribe node can talk to v0.90.\* clusters? ie the tribe functionality is only required on the designated tribe node and not all it's connected clusters. Regards, Mark Walkom Infrastructure Engineer Campaign Monitor email: [markw@campaignmonitor.com](mailto:markw@campaignmonitor.com) web: [www.campaignmonitor.com](http://www.campaignmonitor.com) On 17 January 2014 08:48, [joergprante@gmail.com](mailto:joergprante@gmail.com) [joergprante@gmail.com](mailto:joergprante@gmail.com)wrote: > 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 [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com). > To view this discussion on the web visit > [https://groups.google.com/d/msgid/elasticsearch/CAKdsXoEGg1YuS8Lgom\_XdLCx%3Dk%2BvscQcBGGMWdmUpwN%2BJye\_zA%40mail.gmail.com](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](https://groups.google.com/groups/opt_out). -- 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 [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com). To view this discussion on the web visit [https://groups.google.com/d/msgid/elasticsearch/CAEM624bYH-mxWAOpZD-6Wc-LtEaHrmOxF8RPTPirbtNA5EURpQ%40mail.gmail.com](https://groups.google.com/d/msgid/elasticsearch/CAEM624bYH-mxWAOpZD-6Wc-LtEaHrmOxF8RPTPirbtNA5EURpQ%40mail.gmail.com). For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out). ---
**Author:** ![dadoonet](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/dadoonet/32/137187_2.png) [@dadoonet](https://discuss.elastic.co/u/dadoonet)\ **Post date:** [January 16, 2014, 9:56pm UTC](https://discuss.elastic.co/t/tribe-nodes/15271/6 "2014-01-16T21:56:27Z")
I think it won't work. -- David 😉 Twitter : @dadoonet / @elasticsearchfr / @scrutmydocs Le 16 janv. 2014 à 22:52, Mark Walkom [markw@campaignmonitor.com](mailto:markw@campaignmonitor.com) a écrit : > Does anyone know if a tribe node can talk to v0.90.\* clusters? ie the tribe functionality is only required on the designated tribe node and not all it's connected clusters. > > Regards, > Mark Walkom > > Infrastructure Engineer > Campaign Monitor > email: [markw@campaignmonitor.com](mailto:markw@campaignmonitor.com) > web: [www.campaignmonitor.com](http://www.campaignmonitor.com) > > On 17 January 2014 08:48, [joergprante@gmail.com](mailto:joergprante@gmail.com) [joergprante@gmail.com](mailto:joergprante@gmail.com) wrote: > > > 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 [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com). > > To view this discussion on the web visit [https://groups.google.com/d/msgid/elasticsearch/CAKdsXoEGg1YuS8Lgom\_XdLCx%3Dk%2BvscQcBGGMWdmUpwN%2BJye\_zA%40mail.gmail.com](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](https://groups.google.com/groups/opt_out). > > -- > 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 [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com). > To view this discussion on the web visit [https://groups.google.com/d/msgid/elasticsearch/CAEM624bYH-mxWAOpZD-6Wc-LtEaHrmOxF8RPTPirbtNA5EURpQ%40mail.gmail.com](https://groups.google.com/d/msgid/elasticsearch/CAEM624bYH-mxWAOpZD-6Wc-LtEaHrmOxF8RPTPirbtNA5EURpQ%40mail.gmail.com). > For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out). -- 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 [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com). To view this discussion on the web visit [https://groups.google.com/d/msgid/elasticsearch/38120DBB-C258-4A5F-A57D-8494FF76AA21%40pilato.fr](https://groups.google.com/d/msgid/elasticsearch/38120DBB-C258-4A5F-A57D-8494FF76AA21%40pilato.fr). For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out). ---
**Author:** ![jprante](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/jprante/32/44941_2.png) [@jprante](https://discuss.elastic.co/u/jprante)\ **Post date:** [January 16, 2014, 10:52pm UTC](https://discuss.elastic.co/t/tribe-nodes/15271/7 "2014-01-16T22:52:25Z")
0.90.\* and 1.0.0.RC1 node clients can not talk to each other, discovery fails with errors like [2014-01-16 23:45:40,885][WARN][discovery.zen.ping.multicast] [John Falsworth] failed to read requesting data from /192.168.1.113:54328 java.io.IOException: No transport address mapped to [17519] at org.elasticsearch.common.transport.TransportAddressSerializers.addressFromStream(TransportAddressSerializers.java:71) at org.elasticsearch.cluster.node.DiscoveryNode.readFrom(DiscoveryNode.java:267) at org.elasticsearch.cluster.node.DiscoveryNode.readNode(DiscoveryNode.java:257) at org.elasticsearch.discovery.zen.ping.multicast.MulticastZenPing$Receiver.run(MulticastZenPing.java:410) at java.lang.Thread.run(Thread.java:724) and tribe mode will not magically overcome this situation. 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 [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com). To view this discussion on the web visit [https://groups.google.com/d/msgid/elasticsearch/CAKdsXoF-waXvHv-M6mTYFFa74bG8aBjTK%2Bg6TbPo5Z%3DkCWap4w%40mail.gmail.com](https://groups.google.com/d/msgid/elasticsearch/CAKdsXoF-waXvHv-M6mTYFFa74bG8aBjTK%2Bg6TbPo5Z%3DkCWap4w%40mail.gmail.com). For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out). ---
**Author:** ![Deve\_java](https://avatars.discourse-cdn.com/v4/letter/d/b9bd4f/32.png) [@Deve\_java](https://discuss.elastic.co/u/Deve_java)\ **Post date:** [April 1, 2015, 7:51pm UTC](https://discuss.elastic.co/t/tribe-nodes/15271/8 "2015-04-01T19:51:24Z")
hi members please, how we can use tribe node in java api ? Le jeudi 16 janvier 2014 17:52:25 UTC-5, Jörg Prante a écrit : > 0.90.\* and 1.0.0.RC1 node clients can not talk to each other, discovery > fails with errors like > > [2014-01-16 23:45:40,885][WARN][discovery.zen.ping.multicast] [John > Falsworth] failed to read requesting data from /192.168.1.113:54328 > java.io.IOException: No transport address mapped to [17519] > at > org.elasticsearch.common.transport.TransportAddressSerializers.addressFromStream(TransportAddressSerializers.java:71) > at > org.elasticsearch.cluster.node.DiscoveryNode.readFrom(DiscoveryNode.java:267) > at > org.elasticsearch.cluster.node.DiscoveryNode.readNode(DiscoveryNode.java:257) > at > org.elasticsearch.discovery.zen.ping.multicast.MulticastZenPing$Receiver.run(MulticastZenPing.java:410) > at java.lang.Thread.run(Thread.java:724) > > and tribe mode will not magically overcome this situation. > > 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 [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com). To view this discussion on the web visit [https://groups.google.com/d/msgid/elasticsearch/da91e510-81e3-4bd7-b01e-e2828ad2f0f6%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/da91e510-81e3-4bd7-b01e-e2828ad2f0f6%40googlegroups.com). For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). ---
**Author:** ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)\ **Post date:** [April 1, 2015, 9:11pm UTC](https://discuss.elastic.co/t/tribe-nodes/15271/9 "2015-04-01T21:11:16Z")
Please start your own thread for your question 🙂 On 2 April 2015 at 06:51, Deve java [deve.java2014@gmail.com](mailto:deve.java2014@gmail.com) wrote: > hi members > > please, how we can use tribe node in java api ? > > Le jeudi 16 janvier 2014 17:52:25 UTC-5, Jörg Prante a écrit : > > > 0.90.\* and 1.0.0.RC1 node clients can not talk to each other, discovery > > fails with errors like > > > > [2014-01-16 23:45:40,885][WARN][discovery.zen.ping.multicast] [John > > Falsworth] failed to read requesting data from /192.168.1.113:54328 > > java.io.IOException: No transport address mapped to [17519] > > at org.elasticsearch.common.transport.TransportAddressSerializers. > > addressFromStream(TransportAddressSerializers.java:71) > > at org.elasticsearch.cluster.node.DiscoveryNode.readFrom( > > DiscoveryNode.java:267) > > at org.elasticsearch.cluster.node.DiscoveryNode.readNode( > > DiscoveryNode.java:257) > > at org.elasticsearch.discovery.zen.ping.multicast. > > MulticastZenPing$Receiver.run(MulticastZenPing.java:410) > > at java.lang.Thread.run(Thread.java:724) > > > > and tribe mode will not magically overcome this situation. > > > > 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 [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com). > > To view this discussion on the web visit > > [https://groups.google.com/d/msgid/elasticsearch/da91e510-81e3-4bd7-b01e-e2828ad2f0f6%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/da91e510-81e3-4bd7-b01e-e2828ad2f0f6%40googlegroups.com) > > [https://groups.google.com/d/msgid/elasticsearch/da91e510-81e3-4bd7-b01e-e2828ad2f0f6%40googlegroups.com?utm\_medium=email&utm\_source=footer](https://groups.google.com/d/msgid/elasticsearch/da91e510-81e3-4bd7-b01e-e2828ad2f0f6%40googlegroups.com?utm_medium=email&utm_source=footer) > > . > > For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). -- 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 [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com). To view this discussion on the web visit [https://groups.google.com/d/msgid/elasticsearch/CAEYi1X\_uxzu%2Bhcws9KnrP96n0%2BLqN7xaDMYoYDb-NsXBjLxFRw%40mail.gmail.com](https://groups.google.com/d/msgid/elasticsearch/CAEYi1X_uxzu%2Bhcws9KnrP96n0%2BLqN7xaDMYoYDb-NsXBjLxFRw%40mail.gmail.com). For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [July 6, 2017, 12:22am UTC](https://discuss.elastic.co/t/tribe-nodes/15271/10 "2017-07-06T00:22:18Z")