maria-developers team mailing list archive
Mailing list archive
Re: RFC: Pausing a query thread
I have seen the problems with both MyISAM, InnoDB and even with memory storage.
I want to stop the executing thread instead of implementing the change in the storage engines.
Unfortunately hosting companies can not change the software of their clients and also don't have the manpower to do that.
So a solution for them would only be if it is possible to pause the executing thread until the server calms down.
It is a unique situation where general replies as "Fix your database design", "Optimize your query" or "Upgrade to the
next version" are not possible. It is impossible to fix the enormous amount of software that they are hosting.
On 06/24/2013 03:48 PM, Roberto Spadim wrote:
hum, it's a innodb table? a myisam? what are you talking about high resource? locked tables? high write/read ?
2013/6/24 Marian Marinov <mm@xxxxxxxx <mailto:mm@xxxxxxxx>>
I work with hosting companies and all of my clients have the same irritating problem, one query taking a lot of time
to finish and consuming a lot of resources.
So I have solved the same issue but with processes on the machine by simply pausing(kill -STOP) these processes when
the load is high and continuing(kill -CONT) them when the server load goes down.
I want to implement the same logic within MariaDB, so I can STOP/CONT the thread that is executing this query.
My idea is to implement this in the 'KILL query_id' function, so it will accept one more argument, which will be
either STOP or CONT. If the parameter is not present, the default behavior should remain.
What do you think about my approach?
Mailing list: https://launchpad.net/~maria-__developers <https://launchpad.net/~maria-developers>
Post to : maria-developers@lists.__launchpad.net <mailto:maria-developers@xxxxxxxxxxxxxxxxxxx>
Unsubscribe : https://launchpad.net/~maria-__developers <https://launchpad.net/~maria-developers>
More help : https://help.launchpad.net/__ListHelp <https://help.launchpad.net/ListHelp>