# ProxySQL for Procedure call routing

**URL:** <https://forums.percona.com/t/proxysql-for-procedure-call-routing/31113>\
**Category:** ProxySQL\
**Tags:** community, mysql, percona\
**Created:** [June 20, 2024, 3:45am UTC](https://forums.percona.com/t/proxysql-for-procedure-call-routing/31113 "2024-06-20T03:45:09Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![erpramodprajapat](https://avatars.discourse-cdn.com/v4/letter/e/c37758/32.png) [@erpramodprajapat](https://forums.percona.com/u/erpramodprajapat)\
**Post date:** [June 20, 2024, 3:45am UTC](https://forums.percona.com/t/proxysql-for-procedure-call-routing/31113/1 "2024-06-20T03:45:09Z")

</div>

Our application deals only via procedure, we are planning to use proxysql to route read traffic to secondary node, we are using standard master-slave replication. We have started Test, but we are seeing some issue , sometime its routing sometime not,

1. MySQL connecter sending SET user-defined variables = null ,
2. we have defined query rule for procedure. but still sometime going to master node
3. query\_lock\_to\_hostgroup tried both 0 and 1

Can someone please guide how to use proxysql for procedures

---

<div class="post-metadata">

**Author:** ![matthewb](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/matthewb/32/34_2.png) [@matthewb](https://forums.percona.com/u/matthewb)\
**Post date:** [June 20, 2024, 2:29pm UTC](https://forums.percona.com/t/proxysql-for-procedure-call-routing/31113/2 "2024-06-20T14:29:40Z")

</div>

> [@erpramodprajapat](#):
>
> - MySQL connecter sending SET user-defined variables = null ,

This is most likely causing ProxySQL to route to the source. Can you remove these as a test?

According to [the documentation](https://proxysql.com/Documentation/global-variables/mysql-variables/#mysql-set_query_lock_on_hostgroup), setting this to 0 should force query routing.

Make sure you are not reusing connections. If your connector is also doing connection pooling, this will cause problems. Do not pool connections to a connection pooler.

---

<div class="post-metadata">

**Author:** ![erpramodprajapat](https://avatars.discourse-cdn.com/v4/letter/e/c37758/32.png) [@erpramodprajapat](https://forums.percona.com/u/erpramodprajapat)\
**Post date:** [June 21, 2024, 4:15am UTC](https://forums.percona.com/t/proxysql-for-procedure-call-routing/31113/3 "2024-06-21T04:15:41Z")

</div>

> [@matthewb](#):
>
> ll cause problems. Do not pool connectio

We are using java connection pool, is it required to removed ?

---

<div class="post-metadata">

**Author:** ![matthewb](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/matthewb/32/34_2.png) [@matthewb](https://forums.percona.com/u/matthewb)\
**Post date:** [June 21, 2024, 5:21pm UTC](https://forums.percona.com/t/proxysql-for-procedure-call-routing/31113/4 "2024-06-21T17:21:15Z")

</div>

Required, no. Recommended, yes. You should not connection pool in front of a connection pooler. If you are using the Java connection pooler, then why use proxysql?

---

<div class="post-metadata">

**Author:** ![erpramodprajapat](https://avatars.discourse-cdn.com/v4/letter/e/c37758/32.png) [@erpramodprajapat](https://forums.percona.com/u/erpramodprajapat)\
**Post date:** [June 24, 2024, 3:40am UTC](https://forums.percona.com/t/proxysql-for-procedure-call-routing/31113/5 "2024-06-24T03:40:40Z")

</div>

> [@matthewb](#):
>
> n why use proxysql?

We want to load balance DB traffic, want to divert the read traffic to according to query rules.