On Wed, Oct 26, 2011 at 10:18 PM, Platonides <platonides(a)gmail.com> wrote:
Marlen Caemmerer wrote:
Rosemary (one of the enwiki-DB-Hosts) seems to
bring the maximum of the I/O that is possible, disk graphs are clipping there.
In the MySQL traffic graph you can see there is clipping too.
Strange thing about this is that this phenomenon started in the middle of september. Can
anyone remember any important change in this time?
That is not the case with thyme (other enwiki DB Host) so it'd be a question wether
we could share the load better.
Also I enabled query caching and will see if this is useful in any way.
Maybe there's some job/tool which started at that time which loaded
rosemary so much?
In the last three hours, I got no less than 21 immensely useless mails
from the query killer. The following query, apparently, was killed
after running for a whooping 71 minutes:
SELECT /* SLOW_OK */ /* GLAMOROUS */
globalimagelinks,page,categorylinks where gil_to=page_title and cl_to
page_id=cl_from AND page_namespace=6 AND gil_page_namespace=""
This queries, and others like it, have not caused problems for the
last one (two? I can't remember) years they've been in place.
Something has changed for the far, far worse.