[redwood739]

Well it's partitioned, everything is not in the same folder. We were using flat, they are slow. To be honest I am not sure how much longer we will be using mysql in this case. We'll still have several mysql servers just use a different solution for a few of them.

No worries on the special build, I was just wondering if there was an easier way to strip it out.

thanks,

[redwood739]

well, we have a lot of tables. On one servers we add hundreds a day and we don't drop tables. So the show table status can run for a very long time, hence the “bad things”. Sorry about the lack of clarification. We run monyog on a separate server.

I don't think this is a MONyog thing it's more our environment.

[redwood739]

I am not sure how long. I am just implementing it. I am thinking maybe 60 seconds is pretty long and an alert needs to kick off if a process is still running. I'll need to ask the developer. I found this bash script:

#!/bin/bash

while [ 1 ]

do

mysql -N -u username -ppassword -e 'show processlist' |egrep -v 'Sleep|show processlist'

sleep 2

done

I am thinking we can put this into a perl script.

The issue is the slow query log will tell us after the query has run. We would like to have some kind of alert sent to us when a process is currently running and currently blocking (we use MyISAM).

Does that make sense? Am I making sense? I am a bit more of MS DBA…..

[Author]

Posts