# Multi-Primary Write problem with ProxySQL in the Percona MySQL Operator on Kubernetes **URL:** \ **Category:** Percona Server for MySQL 8.0\ **Tags:** mysql, percona\ **Created:** [January 13, 2026, 4:23am UTC](https://forums.percona.com/t/multi-primary-write-problem-with-proxysql-in-the-percona-mysql-operator-on-kubernetes/40037 "2026-01-13T04:23:27Z")\ **Posts on this page:** 7\ **Page:** 1
**Author:** ![Arsenal\_Dong](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/arsenal_dong/32/22989_2.png) [@Arsenal\_Dong](https://forums.percona.com/u/Arsenal_Dong)\ **Post date:** [January 13, 2026, 4:23am UTC](https://forums.percona.com/t/multi-primary-write-problem-with-proxysql-in-the-percona-mysql-operator-on-kubernetes/40037/1 "2026-01-13T04:23:27Z")
I deployed ProxySQL and MySQL on Kubernetes according to the official documentation, but it always ends up being configured in multi-primary (multi-writer) mode. How can I resolve this problem? SELECT hostgroup\_id, hostname, status FROM mysql\_servers ORDER BY hostgroup\_id; ±-------------±--------------------------------------------------±-------+ | hostgroup\_id | hostname | status | ±-------------±--------------------------------------------------±-------+ | 10 | cluster1-pxc-0.cluster1-pxc.pxc.svc.cluster.local | ONLINE | | 10 | cluster1-pxc-1.cluster1-pxc.pxc.svc.cluster.local | ONLINE | | 10 | cluster1-pxc-2.cluster1-pxc.pxc.svc.cluster.local | ONLINE | | 11 | cluster1-pxc-0.cluster1-pxc.pxc.svc.cluster.local | ONLINE | | 11 | cluster1-pxc-1.cluster1-pxc.pxc.svc.cluster.local | ONLINE | | 11 | cluster1-pxc-2.cluster1-pxc.pxc.svc.cluster.local | ONLINE | | 12 | cluster1-pxc-1.cluster1-pxc.pxc.svc.cluster.local | ONLINE | | 12 | cluster1-pxc-2.cluster1-pxc.pxc.svc.cluster.local | ONLINE | ±-------------±--------------------------------------------------±-------+ ---
**Author:** ![kedarpercona](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/kedarpercona/32/809_2.png) [@kedarpercona](https://forums.percona.com/u/kedarpercona)\ **Post date:** [January 13, 2026, 4:40am UTC](https://forums.percona.com/t/multi-primary-write-problem-with-proxysql-in-the-percona-mysql-operator-on-kubernetes/40037/2 "2026-01-13T04:40:54Z")
Welcome to Percona Forum @Arsenal_Dong , I see that you’re querying mysql\_servers table. That’s for configuration but when you “apply that configuration”, proxysql loads it to runtime and that is the table you should check for active status. Please rerun your query as: `SELECT hostgroup_id, hostname, status FROM ` **`runtime_mysql_servers`** ` ORDER BY hostgroup_id;` Thanks, K Refer: > **[ProxySQL Configuration File & Startup Process Explained | Change Is...](https://kedar.nitty-witty.com/blog/proxysql-configuration-file-startup-process-explained)** > > Master ProxySQL configuration and file management. Learn how proxysql.cnf and SQLite databases interact, simplifying your database admin tasks. > **[Main (runtime tables definition) - ProxySQL](https://proxysql.com/documentation/main-runtime/)** > > Manage ProxySQL's configurations efficiently with admin credentials. Explore tables in Admin for runtime and configuration details. ---
**Author:** ![Arsenal\_Dong](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/arsenal_dong/32/22989_2.png) [@Arsenal\_Dong](https://forums.percona.com/u/Arsenal_Dong)\ **Post date:** [January 13, 2026, 5:06am UTC](https://forums.percona.com/t/multi-primary-write-problem-with-proxysql-in-the-percona-mysql-operator-on-kubernetes/40037/3 "2026-01-13T05:06:18Z")
> [@kedarpercona](#): > > runtime\_mysql\_servers Hi, K Thanks for your answer and reference link sharing! Below is the result to query table runtime\_mysql\_servers: mysql\> SELECT hostgroup\_id, hostname, status FROM runtime\_mysql\_servers ORDER BY hostgroup\_id; ±-------------±--------------------------------------------------±--------+ | hostgroup\_id | hostname | status | ±-------------±--------------------------------------------------±--------+ | 10 | cluster1-pxc-0.cluster1-pxc.pxc.svc.cluster.local | ONLINE | | 10 | cluster1-pxc-1.cluster1-pxc.pxc.svc.cluster.local | ONLINE | | 10 | cluster1-pxc-2.cluster1-pxc.pxc.svc.cluster.local | ONLINE | | 11 | cluster1-pxc-0.cluster1-pxc.pxc.svc.cluster.local | ONLINE | | 11 | cluster1-pxc-1.cluster1-pxc.pxc.svc.cluster.local | SHUNNED | | 11 | cluster1-pxc-2.cluster1-pxc.pxc.svc.cluster.local | SHUNNED | | 12 | cluster1-pxc-1.cluster1-pxc.pxc.svc.cluster.local | ONLINE | | 12 | cluster1-pxc-2.cluster1-pxc.pxc.svc.cluster.local | ONLINE | ±-------------±--------------------------------------------------±--------+ looks like 3 nodes all be written nodes, right？ ---
**Author:** ![kedarpercona](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/kedarpercona/32/809_2.png) [@kedarpercona](https://forums.percona.com/u/kedarpercona)\ **Post date:** [January 13, 2026, 5:35am UTC](https://forums.percona.com/t/multi-primary-write-problem-with-proxysql-in-the-percona-mysql-operator-on-kubernetes/40037/4 "2026-01-13T05:35:51Z")
hmmm! Can you share galera hostgroups configuration? (or the steps that you followed to set this up) `select * from runtime_mysql_galera_hostgroups;` > **[Galera Configuration - ProxySQL](https://proxysql.com/documentation/galera-configuration/)** > > Comprehensive guide on configuring ProxySQL with Galera Cluster for high availability and performance. ---
**Author:** ![Arsenal\_Dong](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/arsenal_dong/32/22989_2.png) [@Arsenal\_Dong](https://forums.percona.com/u/Arsenal_Dong)\ **Post date:** [January 13, 2026, 6:04am UTC](https://forums.percona.com/t/multi-primary-write-problem-with-proxysql-in-the-percona-mysql-operator-on-kubernetes/40037/5 "2026-01-13T06:04:27Z")
![image](https://us1.discourse-cdn.com/flex019/uploads/percona1/original/3X/9/1/9117b8274c2b97d9d7de76b9e7f345e3000a245e.png) ---
**Author:** ![kedarpercona](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/kedarpercona/32/809_2.png) [@kedarpercona](https://forums.percona.com/u/kedarpercona)\ **Post date:** [January 13, 2026, 7:46am UTC](https://forums.percona.com/t/multi-primary-write-problem-with-proxysql-in-the-percona-mysql-operator-on-kubernetes/40037/6 "2026-01-13T07:46:28Z")
So as per your configuration **11 is writer hostgroup**. There you only have 1 node ONLINE. Does this looks OK to you? I think you’re wrongly looking at 10. > [@Arsenal\_Dong](#): > > | 11 | cluster1-pxc-0.cluster1-pxc.pxc.svc.cluster.local | ONLINE | > | 11 | cluster1-pxc-1.cluster1-pxc.pxc.svc.cluster.local | SHUNNED | > | 11 | cluster1-pxc-2.cluster1-pxc.pxc.svc.cluster.local | SHUNNED | Thanks, K ---
**Author:** ![Arsenal\_Dong](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/arsenal_dong/32/22989_2.png) [@Arsenal\_Dong](https://forums.percona.com/u/Arsenal_Dong)\ **Post date:** [January 14, 2026, 2:45am UTC](https://forums.percona.com/t/multi-primary-write-problem-with-proxysql-in-the-percona-mysql-operator-on-kubernetes/40037/7 "2026-01-14T02:45:57Z")
> [@kedarpercona](#): > > So as per your configuration **11 is writer hostgroup**. There you only have 1 node ONLINE. Does this looks OK to you? I think you’re wrongly looking at 10. Ops! It’s my fault. Thanks for your patience guidance!