Freeze Break Request: add long query logging to db-qa01.qa

Tim Flink tflink at redhat.com
Mon Apr 6 23:07:36 UTC 2015


On Mon, 6 Apr 2015 13:38:29 -0600
Tim Flink <tflink at redhat.com> wrote:

> On Mon, 6 Apr 2015 10:33:15 -0600
> Tim Flink <tflink at redhat.com> 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
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 473 bytes
Desc: OpenPGP digital signature
URL: <http://lists.fedoraproject.org/pipermail/infrastructure/attachments/20150406/1d5dff8a/attachment-0001.sig>


More information about the infrastructure mailing list