"query_timeout" error

MySQL & MariaDB Percona Operator for MySQL
,
1

Hello,

I see the following error in my java application logs

SqlExceptionHelper:146 - Query execution was interrupted, query_timeout exceeded

I tried to manually to run the following fix in all the proxysql pods

update global_variables set variable_value = 86400000 where variable_name = ‘mysql-default_query_timeout’;

but the error still exist and the action behind it takes few seconds to load and finish.

Do you know a solution to fix this error.

Also, how can I edit the proxysql configurations so I don’t have to do it manually at each pod?

Thanks

2

Hello montassar

Is the query expected to exceed the timeout?

Unfortunately proxysql configuration could be updated only on pods.

3

please follow https://proxysql.com/documentation/configuring-proxysql/

# Active current in-memory MySQL Variable configuration
LOAD MYSQL VARIABLES TO RUNTIME;

# Save the current in-memory MySQL Variable configuration to disk
SAVE MYSQL VARIABLES TO DISK;
4

With 1.6.0 operator version release it will become possible to update proxy config via cr.yaml. Release is scheduled for Oct, 7th

You can consider DB upgrade for such a feature.

5

@IvanPylypenko thanks for the info, for now I’ll just do it manually until version 1.6.0 get released.

and for your question “Is the query expected to exceed the timeout?” the answer it’s not suppose to !!

@Mykola

Thank you for your suggestion, I run those command.

The query is for a deletion action and it’s still taking a long time to finish.

But I’m not seeing the “query_timeout” error anymore but instead this one “Lock wait timeout exceeded; try restarting transaction”