3 ms·
Stopped reading after story about cron script killing long running db queries - it means this system is a huge mess, where killing request is more simple soluti
by EugeneOZ 11y ago
Stopped reading after story about cron script killing long running db queries - it means this system is a huge mess, where killing request is more simple solution than finding which part of code generates it. I saw such systems and I'm sure it's hopeless state and only as sarcasm I can read "thankful to architecture principles" here.
- shaftoe 11y agoWhy not both? It's not unheard of for a deploy with index issues to cause a load spoke in production. Yes, you need to know about the query to fix it, but also killing runaway queries agree they're obviously orphaned can mean the difference between an outage and a slight site degradation in response times.
- EugeneOZ 11y agoBecause if you killing queries, you can forget about data consistency. And when data is in such condition, we should never call it "good enough way".
- shaftoe 11y agoWhy not both? It's not unheard of for a deploy with index issues to cause a load spoke in production. Yes, you need to know about the query to fix it, but also killing runaway queries agree they're obviously orphaned can mean the difference between an outage and a slight site degradation in response times.