-
-
Notifications
You must be signed in to change notification settings - Fork 291
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Connection timed out #37
Comments
Please open
settings , then run command |
1- Is establishing connection between register , business workers and gateways in synchronous mode ? |
I add settings in Now in start in have the following error
|
What about
|
After add settings in |
May be high load caused the problem. |
Who exactly can help me? Linux expert? Network expert?... |
@walkor still having
|
Default timeout is 3 seconds and can be modified by GatewayWorker\Lib\Gateway::$connectTimeout. |
@walkor is the connection keep a lived? Or it is disconnect and when needed it connected again? |
it is disconnect and when needed it connected again. |
@walkor , How can I change the behavior? closing and establishing connection is not optimized |
sendToClient, sendToUid and sendToGroup will not reconnect. |
For +300k concurrent connection: Set these variables in
Also, change these variables in
And finally, increase TCP buffers in
for more information please refer to https://www.linangran.com/?p=547 |
@walkor In distributed deployment I see the following error when I start new gateways in a new machine
10.10.10.50:2320
is a gateway in another machine and the load is very lowWhen I start new gateway in new machine , all business workers in all machines hangs for 10-15 seconds
I think we have
stream_socket_client
in business worker too and it's in synchronous modeThe text was updated successfully, but these errors were encountered: