Ever since I updated MariaDB, I have been having issues every now and then with queries getting stuck and breaking the website for everyone. What happens is that there is some intensive or problematic query that's started, the /tmp drive gets full (immediately), the query gets stuck, and then every user experiences issues because other queries are waiting for that stuck query to finish and it never does. I have to reboot the entire server to fix it because I'm not even able to kill the process. If I'm not online to fix it for 10 hours, the site experiences errors for 10 hours. Not good! My first question is, shouldn't there be a way for that one query to fail without bringing everyone else down with it? According to this page in MariaDB's documentation, there are three new variables introduced with MariaDB 10.3. idle_transaction_timeout, idle_write_transaction_timeout, and idle_readonly_transaction_timeout. It says the default for them is 0, which means transactions are never killed. Could these be what I need to configure or is it some other setting?
Please sign in to leave a comment.