We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
If two nodes out of three are down, proxysql-tool galera register sets OFFLINE_HARD one of them (as it should), but other one is still ONLINE
proxysql-tool galera register
OFFLINE_HARD
ONLINE
[root@node2 mysql]# systemctl stop mysql [root@node2 mysql]# [root@node3 mysql]# systemctl stop mysql [root@node3 mysql]# [root@proxysql proxysql_tools]# proxysql-tool galera register 2017-08-31 05:01:33,077: ERROR: load_balancing_mode.check_backend():284: (2003, "Can't connect to MySQL server on '192.168.90.3' ([Errno 111] Connection refused)") 2017-08-31 05:01:33,078: ERROR: load_balancing_mode.check_backend():287: Looks like backend hostgroup_id=11, hostname=192.168.90.3, port=3306, status=OFFLINE_HARD, weight=1, compression=0, max_connections=10000, max_replication_lag=0, use_ssl=False, max_latency_ms=0, comment={"admin_status": "OFFLINE_HARD", "role": "Reader"} is unhealthy. Set OFFLINE_HARD status. 2017-08-31 05:01:33,086: ERROR: cli.register():102: Failed to talk to database: (2003, "Can't connect to MySQL server on '192.168.90.3' ([Errno 111] Connection refused)") [root@proxysql proxysql_tools]# proxysql-tool galera server status 2017-08-31 05:04:14,827: INFO: server.server_status():44: Writers: +--------------+--------------+------+--------+--------+-------------+-----------------+---------------------+---------+----------------+------------------------------------------+ | hostgroup_id | hostname | port | status | weight | compression | max_connections | max_replication_lag | use_ssl | max_latency_ms | comment | +--------------+--------------+------+--------+--------+-------------+-----------------+---------------------+---------+----------------+------------------------------------------+ | 10 | 192.168.90.2 | 3306 | ONLINE | 1 | 0 | 10000 | 0 | False | 0 | {"admin_status": null, "role": "Writer"} | +--------------+--------------+------+--------+--------+-------------+-----------------+---------------------+---------+----------------+------------------------------------------+ 2017-08-31 05:04:14,832: INFO: server.server_status():44: Readers: +--------------+--------------+------+--------------+--------+-------------+-----------------+---------------------+---------+----------------+----------------------------------------------------+ | hostgroup_id | hostname | port | status | weight | compression | max_connections | max_replication_lag | use_ssl | max_latency_ms | comment | +--------------+--------------+------+--------------+--------+-------------+-----------------+---------------------+---------+----------------+----------------------------------------------------+ | 11 | 192.168.90.3 | 3306 | OFFLINE_HARD | 1 | 0 | 10000 | 0 | False | 0 | {"admin_status": "OFFLINE_HARD", "role": "Reader"} | | 11 | 192.168.90.4 | 3306 | ONLINE | 1 | 0 | 10000 | 0 | False | 0 | {"admin_status": null, "role": "Reader"} | +--------------+--------------+------+--------------+--------+-------------+-----------------+---------------------+---------+----------------+----------------------------------------------------+
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Description
If two nodes out of three are down,
proxysql-tool galera register
setsOFFLINE_HARD
one of them (as it should), but other one is stillONLINE
What I Did
The text was updated successfully, but these errors were encountered: