5 ms·
I was on a production DB once, and ran SHOW FULL PROCESSLIST, and saw "delete from events" had been running for 4 seconds. I killed the query, and set up that
by knodi123 9y ago
I was on a production DB once, and ran SHOW FULL PROCESSLIST, and saw "delete from events" had been running for 4 seconds. I killed the query, and set up that processlist command to run ever 2 seconds. Sure enough, the delete kept reappearing shortly after I killed it. I wasn't on a laptop, but I knew the culprit was somewhere on my floor of the building, so I grabbed our HR woman who was walking by and told her to watch the query window, and if she saw delete, I showed her how to kill the process. Then I ran out and searched office to office until I found the culprit -
Our CTO thought he was on his local dev box, and was frustrated that "something" was keeping him from clearing out his testing DB.
Did I get a medal for that? No. Nobody wanted to talk about it ever again.
- Demiurge 9y agoSometimes I get reminded about how awesome some of the tech we use is, in this case, transactions :)
- justicezyx 9y agoAnother stupid cto... You did a great job!
- blablabla123 9y agoOh god, this is the worst... People make errors, you help them and they don't give you any credit. Hope you are working somewhere else now.
- lostlogin 9y agoA use for HR!
- S4M 9y agoActually, the CTO should have mailed the dev team saying: Hi, Yesterday, I thought I was on my local machine and clear the database, while I was in fact on the production server. Luckily knodi123 caught it and killed the delete process. This is a reminder that *anybody* can make mistakes, so I want to set up some process to make sure this can't happen, but meanwhile I would like to thank knodil123. Best, CTO