1. 

   cayasanchez, Member

   Good morning MyDBR team:

   We have few reports that sometimes takes too long to show the data, when this happens myDBR can't show any other report.
   We want to configure MyDBR to wait only 60 seconds, if the query takes more than that automatically kill the process.
   I didn't find anything in MyDBR documentation, do you have this option to set the maximum running time for a report?

   I tried adding this statemente before the select, but it didn't work:

   SET STATEMENT max_statement_time = 60 FOR SELECT ....

   Thanks for your help
2. 

   myDBR Team, Key Master

   Long running reports should not block other reports.

   The max_statement_time setting should work for SELECT queries in both MySQL and MariaDB. In MySQL, the parameter is in milliseconds, while in MariaDB, it is in seconds.

   Alternatively, you can use an event to track and handle long-running queries (note that this is applied per query, not the full procedure):

   Set the event_scheduler on:
   

   1.SET GLOBAL event_scheduler = ON;

   Create a procedure that checks long running queries:

   01.create procedure sp_killmax60sec()

   02.begin

   03.declare v_id int;

   04. 

   05.declare done int default 0;

   06. 

   07.declare c_cursor cursor for

   08.  select id

   09.  from INFORMATION_SCHEMA.PROCESSLIST pl

   10.  where COMMAND='Query' and DB='mydbr' and pl.TIME>60;

   11.declare continue handler for not found set done = 1;

   12. 

   13.open c_cursor;

   14.repeat

   15.  fetch c_cursor into v_id;

   16.  if not done then

   17.    kill v_id;

   18.  end if;

   19.until done end repeat;

   20. 

   21.close c_cursor;

   22. 

   23.end

   And then create an event for it:

   1.CREATE EVENT killer ON SCHEDULE EVERY 5 SECOND DO CALL sp_killmax60sec();

   --
   myDBR Team

Reply

You must log in to post.