On Mon, 6 Apr 2015 13:38:29 -0600 Tim Flink <tflink@xxxxxxxxxx> wrote: > On Mon, 6 Apr 2015 10:33:15 -0600 > Tim Flink <tflink@xxxxxxxxxx> wrote: > > > I'm not crazy about doing this during freeze but I'm worried that > > the timeout problem will start affecting more than stg before long > > and want to get this figured out before that happens. > > As an update - I'm not ignoring the +1s, I just managed to stumble on > something I can poke at outside of production when preparing to make > the change on the db server. > > I'm still hoping to avoid changing the db server during freeze, so I'm > going to keep digging into the issue using my local setup now that I > have something I can dig into. > > For anyone who's interested in following along, the issue is being > tracked as: > > https://phab.qadevel.cloud.fedoraproject.org/T452 After much debugging and poking, I think that I've figured out why Taskotron staging is having the issues that it is. The root is still slow queries but instead of modifying the production database, there is a way to change how our code is using those slow queries to keep mod_wsgi from timing out and killing the requests. Since we have a different approach to solving the problem (at least in the short term), I won't be applying the patch to ansible or modifying the database configuration during freeze. Tim
Attachment:
pgpxMpUItphLi.pgp
Description: OpenPGP digital signature
_______________________________________________ infrastructure mailing list infrastructure@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/infrastructure
