# How to use transport client (or something else) to search in ES indices on another system? **URL:** \ **Category:** Elasticsearch\ **Created:** [June 14, 2016, 6:27am UTC](https://discuss.elastic.co/t/how-to-use-transport-client-or-something-else-to-search-in-es-indices-on-another-system/52688 "2016-06-14T06:27:21Z")\ **Posts on this page:** 10\ **Page:** 1
**Author:** ![Vicky2000](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/vicky2000/32/10142_2.png) [@Vicky2000](https://discuss.elastic.co/u/Vicky2000)\ **Post date:** [June 14, 2016, 6:27am UTC](https://discuss.elastic.co/t/how-to-use-transport-client-or-something-else-to-search-in-es-indices-on-another-system/52688/1 "2016-06-14T06:27:21Z")
I searched and found that transport client should do the job. However, I don't know the settings I need to do for the same, both on the another system and my own. Further, it seems that I just can't access any system and will require permission. But I couldn't find anything relevant for this. I am using linux on both the system with elasticsearch 2.3.2, eclipse mars, java 7 built on maven. Please ask if you need more clarification. Thanks in advance for helping. ---
**Author:** ![danielmitterdorfer](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/danielmitterdorfer/32/110510_2.png) [@danielmitterdorfer](https://discuss.elastic.co/u/danielmitterdorfer)\ **Post date:** [June 14, 2016, 9:09am UTC](https://discuss.elastic.co/t/how-to-use-transport-client-or-something-else-to-search-in-es-indices-on-another-system/52688/2 "2016-06-14T09:09:02Z")
Hi @Vicky2000, the [transport client docs](https://www.elastic.co/guide/en/elasticsearch/client/java-api/current/transport-client.html) should get you started. The remote Elasticsearch cluster needs to [bind to a network interface](https://www.elastic.co/guide/en/elasticsearch/reference/current/setup-configuration.html#settings) instead of localhost (you can verify that this is the case by issuing `curl http://remote-cluster-ip:9200/`. This should return basic cluster info. Otherwise the remote Elasticsearch cluster is not reachable. Daniel ---
**Author:** ![Vicky2000](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/vicky2000/32/10142_2.png) [@Vicky2000](https://discuss.elastic.co/u/Vicky2000)\ **Post date:** [June 14, 2016, 1:11pm UTC](https://discuss.elastic.co/t/how-to-use-transport-client-or-something-else-to-search-in-es-indices-on-another-system/52688/3 "2016-06-14T13:11:21Z")
I tried the curl command mentioned by me. I didn't work. That means, remote ES cluster is unreachable. What changes should I make to the another pc so that I may access it from my system? I feel that there must be some settings, as otherwise anyone knowing ip address of a system can access the cluster. ---
**Author:** ![danielmitterdorfer](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/danielmitterdorfer/32/110510_2.png) [@danielmitterdorfer](https://discuss.elastic.co/u/danielmitterdorfer)\ **Post date:** [June 14, 2016, 8:31pm UTC](https://discuss.elastic.co/t/how-to-use-transport-client-or-something-else-to-search-in-es-indices-on-another-system/52688/4 "2016-06-14T20:31:51Z")
Hi @Vicky2000, did you check that the cluster binds to a network interface as I suggested in my answer? Daniel ---
**Author:** ![Vicky2000](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/vicky2000/32/10142_2.png) [@Vicky2000](https://discuss.elastic.co/u/Vicky2000)\ **Post date:** [June 20, 2016, 9:45am UTC](https://discuss.elastic.co/t/how-to-use-transport-client-or-something-else-to-search-in-es-indices-on-another-system/52688/5 "2016-06-20T09:45:44Z")
Hi Daniel! I had been away and just retried your suggestion. Elasticsearch does't run when I bind the remote cluster to a network interface rather than localhost. **This is my ES log when I tried that:** [2016-06-20 14:57:28,021][WARN][bootstrap] Unable to lock JVM Memory: error=12,reason=Cannot allocate memory [2016-06-20 14:57:28,021][WARN][bootstrap] This can result in part of the JVM being swapped out. [2016-06-20 14:57:28,022][WARN][bootstrap] Increase RLIMIT\_MEMLOCK, soft limit: 65536, hard limit: 65536 [2016-06-20 14:57:28,022][WARN][bootstrap] These can be adjusted by modifying /etc/security/limits.conf, for example: # allow user 'varun' mlockall varun soft memlock unlimited varun hard memlock unlimited [2016-06-20 14:57:28,022][WARN][bootstrap] If you are logged in interactively, you will have to re-login for the new limits to take effect. [2016-06-20 14:57:28,359][INFO][node] [varun] version[2.3.2], pid[11569], build[b9e4a6a/2016-04-21T16:03:47Z] [2016-06-20 14:57:28,359][INFO][node] [varun] initializing ... [2016-06-20 14:57:28,943][INFO][plugins] [varun] modules [lang-groovy, reindex, lang-expression], plugins [hq, head], sites [head, hq] [2016-06-20 14:57:28,967][INFO][env] [varun] using [1] data paths, mounts [[/ (/dev/sda6)]], net usable\_space [65.8gb], net total\_space [88.5gb], spins? [possibly], types [ext4] [2016-06-20 14:57:28,967][INFO][env] [varun] heap size [990.7mb], compressed ordinary object pointers [true] Exception in thread "main" java.lang.IllegalArgumentException: Failed to resolve address for [node-1] Likely root cause: java.net.UnknownHostException: node-1: Name or service not known at java.net.Inet6AddressImpl.lookupAllHostAddr(Native Method) at java.net.InetAddress$1.lookupAllHostAddr(InetAddress.java:922) at java.net.InetAddress.getAddressesFromNameService(InetAddress.java:1316) at java.net.InetAddress.getAllByName0(InetAddress.java:1269) at java.net.InetAddress.getAllByName(InetAddress.java:1185) at java.net.InetAddress.getAllByName(InetAddress.java:1119) at org.elasticsearch.transport.netty.NettyTransport.parse(NettyTransport.java:733) at org.elasticsearch.transport.netty.NettyTransport.addressesFromString(NettyTransport.java:685) at org.elasticsearch.transport.TransportService.addressesFromString(TransportService.java:424) at org.elasticsearch.discovery.zen.ping.unicast.UnicastZenPing.(UnicastZenPing.java:160) at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:57) at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45) at java.lang.reflect.Constructor.newInstance(Constructor.java:526) at \<\<\>\> at org.elasticsearch.node.Node.(Node.java:213) at org.elasticsearch.node.Node.(Node.java:140) at org.elasticsearch.node.NodeBuilder.build(NodeBuilder.java:143) at org.elasticsearch.bootstrap.Bootstrap.setup(Bootstrap.java:178) at org.elasticsearch.bootstrap.Bootstrap.init(Bootstrap.java:270) at org.elasticsearch.bootstrap.Elasticsearch.main(Elasticsearch.java:35) ---
**Author:** ![Vicky2000](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/vicky2000/32/10142_2.png) [@Vicky2000](https://discuss.elastic.co/u/Vicky2000)\ **Post date:** [June 20, 2016, 9:51am UTC](https://discuss.elastic.co/t/how-to-use-transport-client-or-something-else-to-search-in-es-indices-on-another-system/52688/6 "2016-06-20T09:51:25Z")
**Not all of them are problematic as this is my ES log when I bind it to localhost and it runs well:** [2016-06-20 14:59:01,901][WARN][bootstrap] Unable to lock JVM Memory: error=12,reason=Cannot allocate memory [2016-06-20 14:59:01,902][WARN][bootstrap] This can result in part of the JVM being swapped out. [2016-06-20 14:59:01,902][WARN][bootstrap] Increase RLIMIT\_MEMLOCK, soft limit: 65536, hard limit: 65536 [2016-06-20 14:59:01,902][WARN][bootstrap] These can be adjusted by modifying /etc/security/limits.conf, for example: # allow user 'varun' mlockall varun soft memlock unlimited varun hard memlock unlimited [2016-06-20 14:59:01,902][WARN][bootstrap] If you are logged in interactively, you will have to re-login for the new limits to take effect. [2016-06-20 14:59:02,205][INFO][node] [varun] version[2.3.2], pid[11610], build[b9e4a6a/2016-04-21T16:03:47Z] [2016-06-20 14:59:02,205][INFO][node] [varun] initializing ... [2016-06-20 14:59:02,796][INFO][plugins] [varun] modules [lang-groovy, reindex, lang-expression], plugins [hq, head], sites [head, hq] ``` **CONT..............** ``` ---
**Author:** ![Vicky2000](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/vicky2000/32/10142_2.png) [@Vicky2000](https://discuss.elastic.co/u/Vicky2000)\ **Post date:** [June 20, 2016, 9:52am UTC](https://discuss.elastic.co/t/how-to-use-transport-client-or-something-else-to-search-in-es-indices-on-another-system/52688/7 "2016-06-20T09:52:50Z")
**.... ES logs continued (bound to localhost)** [2016-06-20 14:59:02,820][INFO][env] [varun] using [1] data paths, mounts [[/ (/dev/sda6)]], net usable\_space [65.8gb], net total\_space [88.5gb], spins? [possibly], types [ext4] [2016-06-20 14:59:02,820][INFO][env] [varun] heap size [990.7mb], compressed ordinary object pointers [true] [2016-06-20 14:59:04,570][INFO][node] [varun] initialized [2016-06-20 14:59:04,570][INFO][node] [varun] starting ... [2016-06-20 14:59:04,629][INFO][transport] [varun] publish\_address {127.0.0.1:9300}, bound\_addresses {127.0.0.1:9300}, {[::1]:9300} [2016-06-20 14:59:04,634][INFO][discovery] [varun] elasticsearch/pYQs1HlhTKiZ6JDMGUm6Bw [2016-06-20 14:59:07,692][INFO][cluster.service] [varun] new\_master {varun}{pYQs1HlhTKiZ6JDMGUm6Bw}{127.0.0.1}{127.0.0.1:9300}, reason: zen-disco-join(elected\_as\_master, [0] joins received) [2016-06-20 14:59:07,708][INFO][http] [varun] publish\_address {127.0.0.1:9200}, bound\_addresses {127.0.0.1:9200}, {[::1]:9200} [2016-06-20 14:59:07,708][INFO][node] [varun] started [2016-06-20 14:59:07,894][INFO][gateway] [varun] recovered [1] indices into cluster\_state [2016-06-20 14:59:08,478][INFO][cluster.routing.allocation] [varun] Cluster health status changed from [RED] to [YELLOW] (reason: [shards started [[.kibana][0]] ...]). ^C[2016-06-20 15:11:45,416][INFO][node] [varun] stopping ... ^C[2016-06-20 15:11:45,597][INFO][node] [varun] stopped [2016-06-20 15:11:45,598][INFO][node] [varun] closing ... [2016-06-20 15:11:45,661][INFO][node] [varun] closed varun@varun-SVE14113ENW:~/elasticsearch-2.3.2/bin$ ./elasticsearch [2016-06-20 15:12:49,245][WARN][bootstrap] Unable to lock JVM Memory: error=12,reason=Cannot allocate memory [2016-06-20 15:12:49,245][WARN][bootstrap] This can result in part of the JVM being swapped out. [2016-06-20 15:12:49,246][WARN][bootstrap] Increase RLIMIT\_MEMLOCK, soft limit: 65536, hard limit: 65536 [2016-06-20 15:12:49,246][WARN][bootstrap] These can be adjusted by modifying /etc/security/limits.conf, for example: # allow user 'varun' mlockall varun soft memlock unlimited varun hard memlock unlimited [2016-06-20 15:12:49,246][WARN][bootstrap] If you are logged in interactively, you will have to re-login for the new limits to take effect. [2016-06-20 15:12:49,796][INFO][node] [varun] version[2.3.2], pid[12042], build[b9e4a6a/2016-04-21T16:03:47Z] [2016-06-20 15:12:49,796][INFO][node] [varun] initializing ... [2016-06-20 15:12:51,025][INFO][plugins] [varun] modules [lang-groovy, reindex, lang-expression], plugins [hq, head], sites [head, hq] [2016-06-20 15:12:51,065][INFO][env] [varun] using [1] data paths, mounts [[/ (/dev/sda6)]], net usable\_space [65.8gb], net total\_space [88.5gb], spins? [possibly], types [ext4] [2016-06-20 15:12:51,085][INFO][env] [varun] heap size [990.7mb], compressed ordinary object pointers [true] [2016-06-20 15:12:55,432][INFO][node] [varun] initialized [2016-06-20 15:12:55,432][INFO][node] [varun] starting ... [2016-06-20 15:12:55,573][INFO][transport] [varun] publish\_address {127.0.0.1:9300}, bound\_addresses {127.0.0.1:9300}, {[::1]:9300} [2016-06-20 15:12:55,578][INFO][discovery] [varun] elasticsearch/BZnOKoWXR8eyYX1GbO2LMg [2016-06-20 15:12:58,643][INFO][cluster.service] [varun] new\_master {varun}{BZnOKoWXR8eyYX1GbO2LMg}{127.0.0.1}{127.0.0.1:9300}, reason: zen-disco-join(elected\_as\_master, [0] joins received) [2016-06-20 15:12:58,672][INFO][http] [varun] publish\_address {127.0.0.1:9200}, bound\_addresses {127.0.0.1:9200}, {[::1]:9200} [2016-06-20 15:12:58,672][INFO][node] [varun] started [2016-06-20 15:12:59,011][INFO][gateway] [varun] recovered [1] indices into cluster\_state [2016-06-20 15:12:59,715][INFO][cluster.routing.allocation] [varun] Cluster health status changed from [RED] to [YELLOW] (reason: [shards started [[.kibana][0]] ...]). ---
**Author:** ![danielmitterdorfer](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/danielmitterdorfer/32/110510_2.png) [@danielmitterdorfer](https://discuss.elastic.co/u/danielmitterdorfer)\ **Post date:** [June 20, 2016, 11:15am UTC](https://discuss.elastic.co/t/how-to-use-transport-client-or-something-else-to-search-in-es-indices-on-another-system/52688/8 "2016-06-20T11:15:33Z")
Hi @Vicky2000, did you see this? > [@Vicky2000](#): > > Exception in thread "main" java.lang.IllegalArgumentException: Failed to resolve address for [node-1]Likely root cause: java.net.UnknownHostException: node-1: Name or service not known I guess you have the following config in your `elasticsearch.yml`: ```auto network : host : node-1 ``` The host name has to be resolvable on the machine on which this Elasticsearch node runs. So you either: - Specify the concrete IP or just "all network interfaces" with `0.0.0.0` - Add the host name to /etc/hosts (on the machine which runs this node) (note: I think this is unpractical but I still add it for completeness sake) - Configure an internal DNS server for resolving node names. I'd recommend the first option to get started. Daniel ---
**Author:** ![Vicky2000](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/vicky2000/32/10142_2.png) [@Vicky2000](https://discuss.elastic.co/u/Vicky2000)\ **Post date:** [June 21, 2016, 9:26am UTC](https://discuss.elastic.co/t/how-to-use-transport-client-or-something-else-to-search-in-es-indices-on-another-system/52688/9 "2016-06-21T09:26:57Z")
Setting the network host to 0.0.0.0 worked. I made a few more changes to the confuguration file and now I can use any of the two PCs as remote host. Thanks a lot @danielmitterdorfer . 🙂 Earlier I had set it to a a random id as was given in the [link](https://www.elastic.co/guide/en/elasticsearch/reference/current/setup-configuration.html#settings). ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [July 5, 2017, 10:41pm UTC](https://discuss.elastic.co/t/how-to-use-transport-client-or-something-else-to-search-in-es-indices-on-another-system/52688/10 "2017-07-05T22:41:47Z")