Zen disco socket usage and port

Elastic Stack Elasticsearch
1

Is it normal for a single node elasticsearch process to open 13 sockets to
itself? This seems like an excessive zen disco party and inexplicable. I am
trying out v1.4.

Is it possible to set the transport protocol port?

--
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.
To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/0db13e63-9d6d-4d60-b05b-a4c0a9bd490a%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

2

More info: I tried to set the transport port like this:
-Dtransport.tcp.port=9999 on the elasticsearch command line, but it still
uses port 9300.

On Tuesday, December 16, 2014 12:42:12 PM UTC-8, Paul Baclace wrote:

Is it normal for a single node elasticsearch process to open 13 sockets to
itself? This seems like an excessive zen disco party and inexplicable. I am
trying out v1.4.

Is it possible to set the transport protocol port?

--
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.
To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/27ea7a90-af23-4989-8d82-c2ba5ca27f75%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

3

ES uses a netty worker pool in order to be able to connect to multiples
nodes. The size of the pool does not automatically take into consideration
that you want a single node cluster only, it does not shrink or grow. You
can reduce the size of the netty worker pool with the
setting transport.netty.worker_count

Any command line parameter must be prefixed by "es." so you should use -
Des.transport.tcp.port=9999

Jörg

On Tue, Dec 16, 2014 at 11:08 PM, Paul Baclace paul.baclace@gmail.com
wrote:

More info: I tried to set the transport port like this:
-Dtransport.tcp.port=9999 on the elasticsearch command line, but it still
uses port 9300.

On Tuesday, December 16, 2014 12:42:12 PM UTC-8, Paul Baclace wrote:

Is it normal for a single node elasticsearch process to open 13 sockets
to itself? This seems like an excessive zen disco party and inexplicable. I
am trying out v1.4.

Is it possible to set the transport protocol port?

--
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.
To view this discussion on the web visit
https://groups.google.com/d/msgid/elasticsearch/27ea7a90-af23-4989-8d82-c2ba5ca27f75%40googlegroups.com
https://groups.google.com/d/msgid/elasticsearch/27ea7a90-af23-4989-8d82-c2ba5ca27f75%40googlegroups.com?utm_medium=email&utm_source=footer
.

For more options, visit 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.
To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/CAKdsXoFYhzGh_6hFHDNMgWwhfYh9r7BQxZk6r-D0V7ZJaPN_4Q%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

4

Now that you pointed out the addition "es." prefix needed when specifying
on the command line, I can see that:
http://www.elasticsearch.org/guide/en/elasticsearch/reference/current/setup-configuration.html
shows it via color in an example and with "instead of". Apparently, that
was not obvious enough for me!

Thanks for the transport.netty.worker_count tip.

--
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.
To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/c5813aa7-a2d8-430f-a801-bca56aecc325%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.