Number of sockets for the clients


(Muzy) #1

If I am creating a node client total number of sockets used is 18 and if I
create a transport client the number of sockets where 9. Is there any way
to reduce the number of sockets for the transport client. Why do I need
this many sockets?

--


(Igor Motov) #2

The number of connections per node is controlled by 3 settings that specify
the number of connections for each connection type (low, med and high)

transport.netty.connections_per_node.low - connections for batch oriented
APIs (like recovery or batch) with high payload that will cause regular
requests (like search or single index) to take longer
*transport.*netty.connections_per_node.med - connections for for the
typical search / single doc index
*transport.*netty.connections_per_node.high - connections for for ping
type requests (like fault detection)

The default settings are low = 2, med = 6 and high = 1

If the number of connections for a given type is set to 0, requests of this
type will use connections of a different type. So, you can, theoretically,
go as low as 0/0/1, but it will, most likely, affect performance.

On Tuesday, October 30, 2012 2:49:35 AM UTC-4, Muzy wrote:

If I am creating a node client total number of sockets used is 18 and if I
create a transport client the number of sockets where 9. Is there any way
to reduce the number of sockets for the transport client. Why do I need
this many sockets?

--


(system) #3