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
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
More info: I tried to set the transport port like this:
-Dtransport.tcp.port= 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
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
