-
Notifications
You must be signed in to change notification settings - Fork 529
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
Dynomite log meaning #798
Comments
proxy_accept : function name I hope I got it all correct. @smukil can confirm. |
Hey @shailesh33 Thanks a lot for the quick reply. Support from you guys would ensure that this community keeps growing. I would really like some help with the below questions. 1.) What do the codes "220" & "343" in the above logs mean?
We had some issue with our system recently due to which a client started bombarding dynomite. As you can see above, max client connections we had set is 1500 and the client requests exceeded this threshold. Dynomite was no longer accepting any redis Commands after this happened. For example on running redis-cli -p 8102 on dynomite box we were getting, "Could not connect to redis at 127.0.0.1:8102. Connection refused". I am attaching a log which helped us debug this. What does the code proxy_accept: 173 mean ? To resolve for this we are going ahead and increasing client_connections to 10000. Question :- Is it possible to configure dynomite such that on exceeding max client requests, it stops accepting new connections but keeps working, instead of completely stopping to work? |
Can someone explain what do these logs mean? Specially the "on event 00FF eof 1 done 1 rb 3536 sb 1221" part ?
proxy_accept:220 accepted CLIENT 14 on PROXY 8 from '10.150.114.162:54142'
[2021-06-24 13:22:14.032] core_close_log:343 close CLIENT 166 '10.150.114.144:41368' on event 00FF eof 1 done 1 rb 3536 sb 1221
The text was updated successfully, but these errors were encountered: