[Openstack] Swift 1.7.4 stable - logging middleware adding lag to final responses
Hi all, We're having a problem when we migrated from 1.4.8, 1.7.4 , and we activated the the proxy-logging middleware On the proxy.log itself we're seeing excelent response times, but it seems that is adding some overhead somewere cause we are seeing on the reques originator that the times are really high. When we turn off the proxy-logging middleware, everything starts to response like a charm 8ms or so vs 800-1400ms !!! And i cant find the way to log locally on debug mode without activating the proxy-logging middleware Ive tried this on the ]DEFAULT] section as the docs says, but im only seeing keystone validations for the ACLs on the log, and none request, with response times are logged set log_name = swift-proxy-server set log_facility = LOG_LOCAL0 set log_level = DEBUG set log_headers = True and set access_log_name = swift-proxy-server set access_log_facility = LOG_LOCAL0 set access_log_level = DEBUG None seems to work, ive tried on the DEFAULT section and on the app.proxy-server section, am i missing something ? Best! Lean ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
Re: [Openstack] Swift 1.7.4 stable - logging middleware adding lag to final responses
On Thu, 10 Jan 2013 12:37:57 -0300 Leandro Reox leandro.r...@gmail.com wrote: When we turn off the proxy-logging middleware, everything starts to response like a charm 8ms or so vs 800-1400ms !!! At a guess, maybe the proxy-logging middle accidentially tries to resolve an IP address somewhere? And i cant find the way to log locally on debug mode without activating the proxy-logging middleware Indeed, in the past I had to resort to custom logging code in instances like that. -- Pete ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
Re: [Openstack] Swift 1.7.4 stable - logging middleware adding lag to final responses
Yep, im planning to debug the current middleware to see if i can submit a fix or find my real problem and if it gets to dirty go to custom logging code Thanks pete Any other experiences will be very appreciated :) On Thu, Jan 10, 2013 at 2:59 PM, Pete Zaitcev zait...@redhat.com wrote: On Thu, 10 Jan 2013 12:37:57 -0300 Leandro Reox leandro.r...@gmail.com wrote: When we turn off the proxy-logging middleware, everything starts to response like a charm 8ms or so vs 800-1400ms !!! At a guess, maybe the proxy-logging middle accidentially tries to resolve an IP address somewhere? And i cant find the way to log locally on debug mode without activating the proxy-logging middleware Indeed, in the past I had to resort to custom logging code in instances like that. -- Pete ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
Re: [Openstack] Swift 1.7.4 stable - logging middleware adding lag to final responses
Does the proxy-logging code use the eventlet.wsgi posthook for the logging? From a quick inspection of the code, it seems to add a generator to the filter layers passing the object along. Could we avoid that by using the posthook? Or was there some other reason for not using the posthook? On Thu, Jan 10, 2013 at 1:24 PM, Leandro Reox leandro.r...@gmail.comwrote: Yep, im planning to debug the current middleware to see if i can submit a fix or find my real problem and if it gets to dirty go to custom logging code Thanks pete Any other experiences will be very appreciated :) On Thu, Jan 10, 2013 at 2:59 PM, Pete Zaitcev zait...@redhat.com wrote: On Thu, 10 Jan 2013 12:37:57 -0300 Leandro Reox leandro.r...@gmail.com wrote: When we turn off the proxy-logging middleware, everything starts to response like a charm 8ms or so vs 800-1400ms !!! At a guess, maybe the proxy-logging middle accidentially tries to resolve an IP address somewhere? And i cant find the way to log locally on debug mode without activating the proxy-logging middleware Indeed, in the past I had to resort to custom logging code in instances like that. -- Pete ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
