When the client and Redis server are connected, what happens when the ephemeral TCP port is not sufficient?

1. The port on the server is always limited, if the Redis server is allocating a zero port in case of large concurrency

2.im service in the server is how to allocate the connection port, a large number of connections, if the temporary port is not enough, whether the other connection is not connected, or the first allocation of a false port, and so on when the implementation of the redistribution

Reply content:

1. The port on the server is always limited, if the Redis server is allocating a zero port in case of large concurrency

2.im service in the server is how to allocate the connection port, a large number of connections, if the temporary port is not enough, whether the other connection is not connected, or the first allocation of a false port, and so on when the implementation of the redistribution

Redis Socket.

This is the case, but in general the single command of Redis takes a short time, with few clients being able to take up the connection without releasing it (the connection pool is an exception, but good), while Redis itself can limit the number of client connections, the default is 10000, and the port range is 1024~ 32768, the number is sufficient, while a single process can open the number of files is also limited, the basic will not exceed the number of ports.
Personally feel that more than the number of ports is still very small, but if this problem occurs in the TCP Connect () error, is a kernel error, the client can not connect to the server at all, so this time the service side can not be allocated false port this processing it.

Provides an article: http://blog.csdn.net/guowake/article/details/6615728

