# Node xxx not part of the cluster Cluster \[elasticsearch\], ignoring **URL:** \ **Category:** Elasticsearch\ **Created:** [June 1, 2011, 7:09am UTC](https://discuss.elastic.co/t/node-xxx-not-part-of-the-cluster-cluster-elasticsearch-ignoring/4514 "2011-06-01T07:09:53Z")\ **Posts on this page:** 4\ **Page:** 1
**Author:** ![Weiwei\_Wang](https://avatars.discourse-cdn.com/v4/letter/w/b19c9b/32.png) [@Weiwei\_Wang](https://discuss.elastic.co/u/Weiwei_Wang)\ **Post date:** [June 1, 2011, 7:09am UTC](https://discuss.elastic.co/t/node-xxx-not-part-of-the-cluster-cluster-elasticsearch-ignoring/4514/1 "2011-06-01T07:09:53Z")
I started two elasticsearch nodes on a remote machine with ip: 10.18.102.134 Then i connect it using TransportClient(java) from ip:10.18.106.36, then the console begins to print warnings as below: [Payne, Frank] Node [#transport#-1][inet[/10.18.102.134:9300]] not part of the cluster Cluster [elasticsearch], ignoring... Another question is how can i get the elasticsearch find nodes in different ip groups, e.g. one node on 10.18.102.134 and the other on 10.18.106.36. ---
**Author:** ![kimchy](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/kimchy/32/44952_2.png) [@kimchy](https://discuss.elastic.co/u/kimchy)\ **Post date:** [June 1, 2011, 1:54pm UTC](https://discuss.elastic.co/t/node-xxx-not-part-of-the-cluster-cluster-elasticsearch-ignoring/4514/2 "2011-06-01T13:54:49Z")
The have different cluster name. If you want the TransportClient to work against more than one node, just add more ips to its list. You can have it sniff out the rest of the nodes as well. All explained here: [Elasticsearch Platform — Find real-time answers at scale | Elastic](http://www.elasticsearch.org/guide/reference/java-api/client.html). On Wednesday, June 1, 2011 at 10:09 AM, Weiwei Wang wrote: > I started two elasticsearch nodes on a remote machine with ip: > 10.18.102.134 > > Then i connect it using TransportClient(java) from ip:10.18.106.36, > then the console begins to print warnings as below: > > [Payne, Frank] Node [#transport#-1][inet[/10.18.102.134:9300]] not > part of the cluster Cluster [elasticsearch], ignoring... > > Another question is > > how can i get the elasticsearch find nodes in different ip groups, > e.g. one node on 10.18.102.134 and the other on 10.18.106.36. ---
**Author:** ![Weiwei\_Wang](https://avatars.discourse-cdn.com/v4/letter/w/b19c9b/32.png) [@Weiwei\_Wang](https://discuss.elastic.co/u/Weiwei_Wang)\ **Post date:** [June 22, 2011, 9:20am UTC](https://discuss.elastic.co/t/node-xxx-not-part-of-the-cluster-cluster-elasticsearch-ignoring/4514/3 "2011-06-22T09:20:08Z")
today i encounter this problem again, i have two cluster: pimsearch and elasticsearch, they are on the same machine group, the differences are that the pimsearch use port 9300 and elasticsearch use 9301. When i use transportclient to connect elasitcsearchIP:3001, the console keep printing: 17:15:54 [elasticsearch[cached]-pool-2-thread-1] WARN org.elasticsearch.client.transport [Slf4jESLogger.java:86]- [Kingo Sunen] Node [Lyja][uwuwaLHDQOi1gt3FC2HOsg][inet[/10.18.102.103:9301]] not part of the cluster Cluster [pimsearch], ignoring... 17:15:54 [elasticsearch[cached]-pool-2-thread-1] WARN org.elasticsearch.client.transport [Slf4jESLogger.java:86]- [Kingo Sunen] Node [Ghost Rider 2099][pn-gpbPlTYWRrK2uAnjgSw][inet[/ 10.18.102.102:9301]] not part of the cluster Cluster [pimsearch], ignoring... 17:15:54 [elasticsearch[cached]-pool-2-thread-1] WARN org.elasticsearch.client.transport [Slf4jESLogger.java:86]- [Kingo Sunen] Node [Abominatrix][7fhUvWx3QBafN7av9EPXcw][inet[/ 10.18.102.101:9301]] not part of the cluster Cluster [pimsearch], ignoring... 17:15:54 [elasticsearch[cached]-pool-2-thread-1] WARN org.elasticsearch.client.transport [Slf4jESLogger.java:86]- [Kingo Sunen] Node [White Tiger][qnTzsokJSw6-tpPtjSh3jA][inet[/ 10.18.102.104:9301]] not part of the cluster Cluster [pimsearch], ignoring... by the way i set client.transport.sniff=true On Jun 1, 9:54 pm, Shay Banon [shay.ba...@elasticsearch.com](mailto:shay.ba...@elasticsearch.com) wrote: > The have different cluster name. > > If you want the TransportClient to work against more than one node, just add more ips to its list. You can have it sniff out the rest of the nodes as well. All explained here:[Elasticsearch Platform — Find real-time answers at scale | Elastic](http://www.elasticsearch.org/guide/reference/java-api/client.html). > > On Wednesday, June 1, 2011 at 10:09 AM, Weiwei Wang wrote: > > > I started two elasticsearch nodes on a remote machine with ip: > > 10.18.102.134 > > > Then i connect it using TransportClient(java) from ip:10.18.106.36, > > then the console begins to print warnings as below: > > > [Payne, Frank] Node [#transport#-1][inet[/10.18.102.134:9300]] not > > part of the cluster Cluster [elasticsearch], ignoring... > > > Another question is > > > how can i get the elasticsearch find nodes in different ip groups, > > e.g. one node on 10.18.102.134 and the other on 10.18.106.36. ---
**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, 4:02am UTC](https://discuss.elastic.co/t/node-xxx-not-part-of-the-cluster-cluster-elasticsearch-ignoring/4514/4 "2017-07-06T04:02:57Z")