# Avoid/Remove inter-node communication in elasticsearch **URL:** \ **Category:** Elasticsearch\ **Created:** [March 19, 2019, 4:31am UTC](https://discuss.elastic.co/t/avoid-remove-inter-node-communication-in-elasticsearch/172893 "2019-03-19T04:31:42Z")\ **Posts on this page:** 17\ **Page:** 1
**Author:** ![MKU](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/mku/32/48327_2.png) [@MKU](https://discuss.elastic.co/u/MKU)\ **Post date:** [March 19, 2019, 4:31am UTC](https://discuss.elastic.co/t/avoid-remove-inter-node-communication-in-elasticsearch/172893/1 "2019-03-19T04:31:42Z")
Hi, I am looking for a way to avoid inter-node communication (that happens through port 9300), Is there a way to block this. Thanks ---
**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:** [March 19, 2019, 4:32am UTC](https://discuss.elastic.co/t/avoid-remove-inter-node-communication-in-elasticsearch/172893/2 "2019-03-19T04:32:39Z")
What's your aim for doing that? ---
**Author:** ![MKU](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/mku/32/48327_2.png) [@MKU](https://discuss.elastic.co/u/MKU)\ **Post date:** [March 19, 2019, 4:35am UTC](https://discuss.elastic.co/t/avoid-remove-inter-node-communication-in-elasticsearch/172893/3 "2019-03-19T04:35:36Z")
As of now i need only one node for testing and development purposes, and taking security into consideration i want to block inter-node communication(also i have completely removed x-pack as well). ---
**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:** [March 19, 2019, 4:37am UTC](https://discuss.elastic.co/t/avoid-remove-inter-node-communication-in-elasticsearch/172893/4 "2019-03-19T04:37:02Z")
If you don't have other nodes listed in the unicast list, then the existing node will not try to contact any others. ---
**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:** [March 19, 2019, 4:40am UTC](https://discuss.elastic.co/t/avoid-remove-inter-node-communication-in-elasticsearch/172893/6 "2019-03-19T04:40:54Z")
You will need a firewall on the host then. ---
**Author:** ![MKU](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/mku/32/48327_2.png) [@MKU](https://discuss.elastic.co/u/MKU)\ **Post date:** [March 19, 2019, 4:46am UTC](https://discuss.elastic.co/t/avoid-remove-inter-node-communication-in-elasticsearch/172893/7 "2019-03-19T04:46:14Z")
Thank you for your reply,is it the only way ---
**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:** [March 19, 2019, 4:47am UTC](https://discuss.elastic.co/t/avoid-remove-inter-node-communication-in-elasticsearch/172893/8 "2019-03-19T04:47:00Z")
The only other option would be to listen on `localhost`. ---
**Author:** ![MKU](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/mku/32/48327_2.png) [@MKU](https://discuss.elastic.co/u/MKU)\ **Post date:** [March 19, 2019, 6:03am UTC](https://discuss.elastic.co/t/avoid-remove-inter-node-communication-in-elasticsearch/172893/9 "2019-03-19T06:03:08Z")
I blocked the port in firewall but still its listening on port 9300. ---
**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:** [March 19, 2019, 7:07am UTC](https://discuss.elastic.co/t/avoid-remove-inter-node-communication-in-elasticsearch/172893/10 "2019-03-19T07:07:43Z")
> i have completely removed x-pack as well Why not downloading the OSS version then? ---
**Author:** ![MKU](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/mku/32/48327_2.png) [@MKU](https://discuss.elastic.co/u/MKU)\ **Post date:** [March 19, 2019, 7:23am UTC](https://discuss.elastic.co/t/avoid-remove-inter-node-communication-in-elasticsearch/172893/11 "2019-03-19T07:23:32Z")
no i am debugging elasticsearch in eclipse. ---
**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:** [March 19, 2019, 8:01am UTC](https://discuss.elastic.co/t/avoid-remove-inter-node-communication-in-elasticsearch/172893/12 "2019-03-19T08:01:41Z")
You can't stop it listening on 9300. You can only block external access to it. ---
**Author:** ![MKU](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/mku/32/48327_2.png) [@MKU](https://discuss.elastic.co/u/MKU)\ **Post date:** [March 20, 2019, 10:01am UTC](https://discuss.elastic.co/t/avoid-remove-inter-node-communication-in-elasticsearch/172893/13 "2019-03-20T10:01:03Z")
I tried to stop binding of socketaddress . and it threw me this error, **BindTransportException[Failed to bind to [9300]]; nested: NullPointerException;** Is there any reason why i can't stop listening through transport layer. ---
**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:** [March 20, 2019, 10:20am UTC](https://discuss.elastic.co/t/avoid-remove-inter-node-communication-in-elasticsearch/172893/14 "2019-03-20T10:20:19Z")
This is not supported I think. What did you do? Did you modify elasticsearch code? ---
**Author:** ![MKU](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/mku/32/48327_2.png) [@MKU](https://discuss.elastic.co/u/MKU)\ **Post date:** [March 20, 2019, 10:33am UTC](https://discuss.elastic.co/t/avoid-remove-inter-node-communication-in-elasticsearch/172893/15 "2019-03-20T10:33:17Z")
Yes i did modify netty code for transport. Actually i dont want inter-node communication to happen,I have been trying many things but nothing seems to be working. ---
**Author:** ![MKU](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/mku/32/48327_2.png) [@MKU](https://discuss.elastic.co/u/MKU)\ **Post date:** [March 20, 2019, 10:43am UTC](https://discuss.elastic.co/t/avoid-remove-inter-node-communication-in-elasticsearch/172893/16 "2019-03-20T10:43:49Z")
Can't we run elasticsearch without communication through 9300, that is just through rest. ---
**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:** [March 20, 2019, 10:51am UTC](https://discuss.elastic.co/t/avoid-remove-inter-node-communication-in-elasticsearch/172893/17 "2019-03-20T10:51:10Z")
> Yes i did modify netty code for transport. Then you introduced most likely the `NullPointerException`. > Can't we run elasticsearch without communication through 9300, that is just through rest. No you can't. The only settings you can work with are: [Transport | Elasticsearch Guide [8.11] | Elastic](https://www.elastic.co/guide/en/elasticsearch/reference/current/modules-transport.html) > Actually i dont want inter-node communication to happen,I have been trying many things but nothing seems to be working. I got that. That's IMO a waste of your time. Just block 9300 on a firewall level and you'll be sure that no one would be able to access your machine. But as already said you can easily do: ```auto network.host: your_ip transport.host: localhost ``` Then you can test from another machine if you can reach 9300 using telnet. I'm sure you won't be able. ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [April 17, 2019, 10:51am UTC](https://discuss.elastic.co/t/avoid-remove-inter-node-communication-in-elasticsearch/172893/18 "2019-04-17T10:51:20Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.