On 2/21/20 5:14 PM, Arthur Smith wrote: > One question - I seem to be getting some more timeout-related 500 server > errors. > Was there a change in how that is handled somehow (i.e. reduced time limit for > response from the server)? I realize it's good practice to respond quickly, > just > some of the existing cases don't at the moment and I'm hitting them > occasionally. >
There are at least 3 proxies involved in serving Toolforge webservices requests: 1) tool main front proxy (dynamicproxy) (http) 2) kubernetes front haproxy (tcp) 3) kubernetes nginx-ingress (http) and perhaps kube-proxy (tcp) More information here: https://wikitech.wikimedia.org/wiki/Portal:Toolforge/Admin/Networking_and_ingress This is to say, yes, serving your request as soon as possible should help the different proxy connections to don't die and work smoothly. As of this email, we don't have any particular metrics or insights on proxies performances and this is something we could explore in the near future (create a specific grafana dashboard or something). regards. -- Arturo Borrero Gonzalez SRE / Wikimedia Cloud Services Wikimedia Foundation _______________________________________________ Wikimedia Cloud Services mailing list Cloud@lists.wikimedia.org (formerly lab...@lists.wikimedia.org) https://lists.wikimedia.org/mailman/listinfo/cloud
