Hello, At Sunday 14 August 2011 20:24:10 DaB. wrote:
So the max run-time is dependent on replag. But, considering this: Replag s3 6050h 10m 44s
I guess you have that replag-value by brian. I have no idea, how he got to this value (I think he uses a non-avaible database), but the replag is MUCH lower (arround 1h at the moment). You find the replag of the kill-time in the eMail BTW.
I currently get bombarded with killed-query-mails
I'm sorry for that. But if I look in the log I see either CREATE-, INSERTS- or DELETE-queries by you without SLOW_OK (a bad idea) or SELECTS which had run for over 30 minutes (the user will be long gone). So please add SLOW_OKs to the CREATE, INSERT, UPDATE, REPLACE etc.pp.-queries and a reasonable LIMIT: to the SELECTs (and try to optimize them) and the mail-flood will ebbing. If you run SELECTs which will take long (from the command-line for example or from SGE) please add also an SLOW_OK – don't do this for webqueries!
Sincerly, DaB.