proxysql

Commit Graph

Author	SHA1	Message	Date
René Cannaò	eac6e75dad	Adding a simulator for read_only test This commit introduces a first simulator for read_only monitoring ProxySQL itself will simulate hundreds of backends across hundreds of hostgroups, all configured in hundreds of clusters, and return read_only values for each of the simulated backend. The read_only value can be configured in table READONLY_STATUS available in the SQLite3Server module. If a backend isn't configured in table READONLY_STATUS , its default read_only value is 1. It is possible to simulate a lot of simultaneous failover running queries like the following: UPDATE READONLY_STATUS SET read_only=1; CREATE TABLE t1 AS SELECT hostname FROM READONLY_STATUS ORDER BY RANDOM() LIMIT 50; UPDATE READONLY_STATUS SET read_only=0 WHERE hostname IN (SELECT hostname FROM t1); DROP TABLE t1;	5 years ago

Author

SHA1

Message

Date

René Cannaò

eac6e75dad

Adding a simulator for read_only test

This commit introduces a first simulator for read_only monitoring

ProxySQL itself will simulate hundreds of backends across hundreds of
hostgroups, all configured in hundreds of clusters, and return read_only
values for each of the simulated backend.
The read_only value can be configured in table READONLY_STATUS available in
the SQLite3Server module.

If a backend isn't configured in table READONLY_STATUS , its default read_only
value is 1.

It is possible to simulate a lot of simultaneous failover running queries like
the following:

UPDATE READONLY_STATUS SET read_only=1;
CREATE TABLE t1 AS SELECT hostname FROM READONLY_STATUS ORDER BY RANDOM() LIMIT 50;
UPDATE READONLY_STATUS SET read_only=0 WHERE hostname IN (SELECT hostname FROM t1);
DROP TABLE t1;

1 Commits (8a0e326ce54c26fa86ec1035c6eefa6b1069cb10)