all mysql servers nodes are showing shunned status

Deepu Choudhary

unread,

Jul 11, 2018, 6:22:33 AM7/11/18

to proxysql

I have a setup of percona cluster with three nodes three nodes. one other server i have installed proxysql but while checking the status it looks like this

proxysql --version

ProxySQL version 1.4.4-139-ga51b040, codename Truls

ProxySQLAdmin> SELECT * FROM runtime_mysql_servers;

+--------------+----------------+------+---------+--------+-------------+-----------------+---------------------+---------+----------------+---------+

+--------------+----------------+------+---------+--------+-------------+-----------------+---------------------+---------+----------------+---------+

| 2 | 192.168.110.32 | 3306 | SHUNNED | 1 | 0 | 1000 | 0 | 0 | 0 | |

| 2 | 192.168.110.34 | 3306 | SHUNNED | 1 | 0 | 1000 | 0 | 0 | 0 | |

| 2 | 192.168.110.33 | 3306 | SHUNNED | 1 | 0 | 1000 | 0 | 0 | 0 | |

+--------------+----------------+------+---------+--------+-------------+-----------------+---------------------+---------+----------------+---------+

3 rows in set (0.01 sec)

ProxySQLAdmin> SELECT * FROM stats_mysql_connection_pool\G

*************************** 1. row ***************************

hostgroup: 2

srv_host: 192.168.110.32

srv_port: 3306

status: SHUNNED

ConnUsed: 0

ConnFree: 0

ConnOK: 0

ConnERR: 0

Queries: 0

Bytes_data_sent: 0

Bytes_data_recv: 0

Latency_us: 0

*************************** 2. row ***************************

hostgroup: 2

srv_host: 192.168.110.33

srv_port: 3306

status: SHUNNED

ConnUsed: 0

ConnFree: 0

ConnOK: 0

ConnERR: 0

Queries: 0

Bytes_data_sent: 0

Bytes_data_recv: 0

Latency_us: 0

*************************** 3. row ***************************

hostgroup: 2

srv_host: 192.168.110.34

srv_port: 3306

status: SHUNNED

ConnUsed: 0

ConnFree: 0

ConnOK: 0

ConnERR: 0

Queries: 0

Bytes_data_sent: 0

Bytes_data_recv: 0

Latency_us: 0

3 rows in set (0.01 sec)

I have created one user in one of the cluster node as:

CREATE USER 'monitor'@'%' IDENTIFIED BY 'monitor';

GRANT SELECT on sys.* to 'monitor'@'%';

FLUSH PRIVILEGES;

:/var/lib/proxysql# tail -f proxysql.log

2018-07-11 15:51:25 MySQL_Monitor.cpp:1362:monitor_ping(): [ERROR] Server 192.168.110.34:3306 missed 3 heartbeats, shunning it and killing all the connections

2018-07-11 15:51:27 MySQL_Monitor.cpp:1362:monitor_ping(): [ERROR] Server 192.168.110.32:3306 missed 3 heartbeats, shunning it and killing all the connections

2018-07-11 15:51:27 MySQL_Monitor.cpp:1362:monitor_ping(): [ERROR] Server 192.168.110.33:3306 missed 3 heartbeats, shunning it and killing all the connections

2018-07-11 15:51:27 MySQL_Monitor.cpp:1362:monitor_ping(): [ERROR] Server 192.168.110.34:3306 missed 3 heartbeats, shunning it and killing all the connections

2018-07-11 15:51:29 MySQL_Monitor.cpp:1362:monitor_ping(): [ERROR] Server 192.168.110.32:3306 missed 3 heartbeats, shunning it and killing all the connections

2018-07-11 15:51:29 MySQL_Monitor.cpp:1362:monitor_ping(): [ERROR] Server 192.168.110.33:3306 missed 3 heartbeats, shunning it and killing all the connections

2018-07-11 15:51:29 MySQL_Monitor.cpp:1362:monitor_ping(): [ERROR] Server 192.168.110.34:3306 missed 3 heartbeats, shunning it and killing all the connections

2018-07-11 15:51:31 MySQL_Monitor.cpp:1362:monitor_ping(): [ERROR] Server 192.168.110.32:3306 missed 3 heartbeats, shunning it and killing all the connections

2018-07-11 15:51:31 MySQL_Monitor.cpp:1362:monitor_ping(): [ERROR] Server 192.168.110.33:3306 missed 3 heartbeats, shunning it and killing all the connections

2018-07-11 15:51:31 MySQL_Monitor.cpp:1362:monitor_ping(): [ERROR] Server 192.168.110.34:3306 missed 3 heartbeats, shunning it and killing all the connections

2018-07-11 15:51:33 MySQL_Monitor.cpp:1362:monitor_ping(): [ERROR] Server 192.168.110.32:3306 missed 3 heartbeats, shunning it and killing all the connections

can you please help on the same

Nikolaos Vyzas

unread,

Jul 11, 2018, 5:33:52 PM7/11/18

to proxysql

If using ProxySQL version 1.4.x please have a look into this article and make you've followed all steps: http://www.proxysql.com/blog/galera-awareness-and-proxysql-scheduler

In version 2.0 native Galera / PXC support will be available with specific hostgroups for this purpose.

Message has been deleted

Deepu Choudhary

unread,

Jul 12, 2018, 2:31:49 AM7/12/18

to proxysql

now after all the nodes are online while connecting through proxysql

mysql -u deepu -p -h 127.0.0.1 -P 6033 --prompt='ProxySQLClient> '

ProxySQLClient> show databases;

ERROR 9001 (HY000): Max connect timeout reached while reaching hostgroup 0 after 10000ms

Can you please help on the same

Ashwini Ahire

unread,

Jul 12, 2018, 11:16:48 PM7/12/18

to Deepu Choudhary, proxysql

Hope this will help: https://github.com/sysown/proxysql/wiki/Frequently-Asked-Questions#11-no-hostgrop-0-has-been-configured--then-why-we-get-max-connect-timeout-reached-while-reaching-hostgroup-0-after-10000ms--

On Thu, Jul 12, 2018 at 2:30 PM, Deepu Choudhary <choudha...@gmail.com> wrote:

now after all the nodes are online while connecting through proxysql

mysql -u deepu -p -h 127.0.0.1 -P 6033 --prompt='ProxySQLClient> '

ProxySQLClient> show databases;
ERROR 9001 (HY000): Max connect timeout reached while reaching hostgroup 0 after 10000ms

Can you please help on the same

On Thursday, 12 July 2018 03:03:52 UTC+5:30, Nikolaos Vyzas wrote:

--
You received this message because you are subscribed to the Google Groups "proxysql" group.
To unsubscribe from this group and stop receiving emails from it, send an email to proxysql+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

--

Regards,

Ashwini Ahire

Reply all

Reply to author

Forward