You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I don't think this is within the scope of the project and don't plan to add it
The redis slowlog feature is the time take on the server - the time taken on the client will vary widely for reasons outside the control of twemproxy, such as network packet loss causing delays (not applicable within the server's own counting, that's counting just time to process the request, compute/encode the response), high cpu load in unrelated programs causing delays, etc., and may be inactionable.
Twemproxy's logging is disabled at verbose level at compile time by default (see ./configure --enable-debug=..., and is skipped based on the nutcracker -v $level option. This would add additional time to processing each request for a feature that would be used pretty rarely and have the drawbacks in 2.
1 and 2, I do not think so. This feature is used for Judge whether the reason is from client to proxy or proxy to server when causing delays.
3. yeap, but it is for every request. Sometime we only care about a certain range of timeout request.
Problem:
Sometimes we need to check what response was slowly, but tweproxy now only support log(every request), it`s very inconvenient.
Solution:
Provide slowlog command like redis slowlog command and return.
I have implemented the redis part , like this:
I`ll sort my code and send it out!
The text was updated successfully, but these errors were encountered: