# "query\_timeout" error

**URL:** <https://forums.percona.com/t/query-timeout-error/8097>\
**Category:** Percona Operator for MySQL\
**Tags:** mysql, percona\
**Created:** [October 2, 2020, 9:31pm UTC](https://forums.percona.com/t/query-timeout-error/8097 "2020-10-02T21:31:16Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![montassar](https://avatars.discourse-cdn.com/v4/letter/m/bbce88/32.png) [@montassar](https://forums.percona.com/u/montassar)\
**Post date:** [October 2, 2020, 9:31pm UTC](https://forums.percona.com/t/query-timeout-error/8097/1 "2020-10-02T21:31:16Z")

</div>

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

---

<div class="post-metadata">

**Author:** ![Ivan\_Pylypenko](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/ivan_pylypenko/32/2452_2.png) [@Ivan\_Pylypenko](https://forums.percona.com/u/Ivan_Pylypenko)\
**Post date:** [October 6, 2020, 4:44am UTC](https://forums.percona.com/t/query-timeout-error/8097/2 "2020-10-06T04:44:10Z")

</div>

Hello montassar

Is the query expected to exceed the timeout?

Unfortunately proxysql configuration could be updated only on pods.

---

<div class="post-metadata">

**Author:** ![Mykola](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/mykola/32/30_2.png) [@Mykola](https://forums.percona.com/u/Mykola)\
**Post date:** [October 6, 2020, 5:05am UTC](https://forums.percona.com/t/query-timeout-error/8097/3 "2020-10-06T05:05:32Z")

</div>

please follow [https://proxysql.com/](https://proxysql.com/)[documentation/configuring-proxysql/](https://proxysql.com/documentation/configuring-proxysql/)

```auto
# 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;

```

---

<div class="post-metadata">

**Author:** ![Ivan\_Pylypenko](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/ivan_pylypenko/32/2452_2.png) [@Ivan\_Pylypenko](https://forums.percona.com/u/Ivan_Pylypenko)\
**Post date:** [October 6, 2020, 5:20am UTC](https://forums.percona.com/t/query-timeout-error/8097/4 "2020-10-06T05:20:07Z")

</div>

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.

---

<div class="post-metadata">

**Author:** ![montassar](https://avatars.discourse-cdn.com/v4/letter/m/bbce88/32.png) [@montassar](https://forums.percona.com/u/montassar)\
**Post date:** [October 15, 2020, 3:58pm UTC](https://forums.percona.com/t/query-timeout-error/8097/5 "2020-10-15T15:58:43Z")

</div>

@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”