Once again, a question on query killer. Below its report informs that with near-zero replag a very simple count(*) only query on s6 takes too long, and the killer expects SLOW_OK would help.

I think something is wrong fundamentally once such a query takes that long, and there is no reason to add SLOW_OK and wait even longer.

mashiah

---------- Forwarded message ---------- From: no-reply@toolserver.org Date: Sat, Nov 5, 2011 at 1:28 AM Subject: [TS] Killed SQL-Task 15233729 on db-server z-dat-s6-a To: mashiah@toolserver.org

Hello mashiah, a MySQL-query of yours was killed because you didn't mark it as SLOW_OK and it have run for 853 seconds which was longer than allowed. You can find the query below. Please have also a look at [1] to find information how you can avoid killings of your queries. Maybe you can optimze the query too? The replication lag at kill-time was 33s.

Sincerly, Query-Killer. This eMail was sent automaticaly, please don't reply.

SELECT count(*) INTO @tl_count FROM ruwiki_p.templatelinks

[1] https://wiki.toolserver.org/view/Database_access#Slow_queries_and_the_query_...