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
Hello,
I'm using proxysql docker image, version 2.7.1.
I'm starting mysql servers with different weight. One node goes down, once the node is up again, the server is re-added with a weight of 1.
Is there a way to retain the weight had before removal?
Full log below.
Many thanks, Marius
proxysql-1 | 2024-10-23 17:18:17 [INFO] Using jemalloc with MALLOC_CONF: config.xmalloc:1, lg_tcache_max:16, opt.prof_accum:1, opt.prof_leak:1, opt.lg_prof_sample:20, opt.lg_prof_interval:30, rc:0 proxysql-1 | 2024-10-23 17:18:17 [INFO] Using config file /etc/proxysql.cnf proxysql-1 | 2024-10-23 17:18:17 [INFO] Current RLIMIT_NOFILE: 1048576 proxysql-1 | 2024-10-23 17:18:17 [INFO] Using OpenSSL version: OpenSSL 3.3.1 4 Jun 2024 proxysql-1 | 2024-10-23 17:18:17 [INFO] SSL keys/certificates found in datadir (/var/lib/proxysql): loading them. proxysql-1 | 2024-10-23 17:18:17 [INFO] ProxySQL version 2.7.1-16-g2726c27 proxysql-1 | 2024-10-23 17:18:17 [INFO] Detected OS: Linux e5093a3402bb 5.15.0-118-generic #128-Ubuntu SMP Fri Jul 5 09:28:59 UTC 2024 x86_64 proxysql-1 | 2024-10-23 17:18:17 [INFO] ProxySQL SHA1 checksum: b707c29266a569f8cf279e1448dbeed31d980e96 proxysql-1 | 2024-10-23 17:18:17 [INFO] SSL keys/certificates found in datadir (/var/lib/proxysql): loading them. proxysql-1 | 2024-10-23 17:18:17 [INFO] Loaded built-in SQLite3 proxysql-1 | Standard ProxySQL MySQL Logger rev. 2.5.0421 -- MySQL_Logger.cpp -- Fri Sep 20 15:51:19 2024 proxysql-1 | Standard ProxySQL Cluster rev. 0.4.0906 -- ProxySQL_Cluster.cpp -- Fri Sep 20 15:51:19 2024 proxysql-1 | Standard ProxySQL Statistics rev. 1.4.1027 -- ProxySQL_Statistics.cpp -- Fri Sep 20 15:51:19 2024 proxysql-1 | 2024-10-23 17:18:17 [INFO] Using UUID from database: 0686bc0c-5f4a-470d-9373-2e5f50fb2900 proxysql-1 | 2024-10-23 17:18:17 [INFO] Computed checksum for 'LOAD ADMIN VARIABLES TO RUNTIME' was '0x6442989A35CF9604', with epoch '1729703897' proxysql-1 | 2024-10-23 17:18:17 [INFO] Computed checksum for 'LOAD MYSQL VARIABLES TO RUNTIME' was '0x87F2C4C1D39088C3', with epoch '1729703897' proxysql-1 | Standard ProxySQL Admin rev. 2.0.6.0805 -- ProxySQL_Admin.cpp -- Fri Sep 20 15:51:19 2024 proxysql-1 | 2024-10-23 17:18:17 [INFO] ProxySQL SHA1 checksum: b707c29266a569f8cf279e1448dbeed31d980e96 proxysql-1 | Standard MySQL Threads Handler rev. 0.2.0902 -- MySQL_Thread.cpp -- Fri Sep 20 15:51:19 2024 proxysql-1 | Standard MySQL Authentication rev. 0.2.0902 -- MySQL_Authentication.cpp -- Fri Sep 20 15:51:19 2024 proxysql-1 | 2024-10-23 17:18:17 [INFO] Computed checksum for 'LOAD MYSQL USERS TO RUNTIME' was '0x58CBB87C308C4B97', with epoch '1729703897' proxysql-1 | 2024-10-23 17:18:17 [INFO] Generating runtime mysql servers and mysql servers v2 records. proxysql-1 | 2024-10-23 17:18:17 [INFO] Dumping mysql_servers_incoming proxysql-1 | +--------------+-----------+------+-----------+--------+--------+-------------+-----------------+---------------------+---------+----------------+---------+ proxysql-1 | | hostgroup_id | hostname | port | gtid_port | weight | status | compression | max_connections | max_replication_lag | use_ssl | max_latency_ms | comment | proxysql-1 | +--------------+-----------+------+-----------+--------+--------+-------------+-----------------+---------------------+---------+----------------+---------+ proxysql-1 | | 1 | 10.1.1.2 | 3306 | 0 | 900 | 0 | 0 | 1000 | 0 | 1 | 0 | | proxysql-1 | | 1 | 10.1.1.3 | 3306 | 0 | 500 | 0 | 0 | 1000 | 0 | 1 | 0 | | proxysql-1 | | 2 | 10.1.1.2 | 3306 | 0 | 1 | 0 | 0 | 1000 | 0 | 1 | 0 | | proxysql-1 | | 2 | 10.1.1.3 | 3306 | 0 | 1 | 0 | 0 | 1000 | 0 | 1 | 0 | | proxysql-1 | +--------------+-----------+------+-----------+--------+--------+-------------+-----------------+---------------------+---------+----------------+---------+ proxysql-1 | 2024-10-23 17:18:17 [INFO] Dumping mysql_servers LEFT JOIN mysql_servers_incoming proxysql-1 | +-------------+--------------+----------+------+ proxysql-1 | | mem_pointer | hostgroup_id | hostname | port | proxysql-1 | +-------------+--------------+----------+------+ proxysql-1 | +-------------+--------------+----------+------+ proxysql-1 | 2024-10-23 17:18:17 [INFO] Dumping mysql_servers JOIN mysql_servers_incoming proxysql-1 | +--------------+-----------+------+-----------+--------+--------+-------------+-----------------+---------------------+---------+----------------+---------+-------------+-----------+--------+--------+-------------+-----------------+---------------------+---------+----------------+---------+ proxysql-1 | | hostgroup_id | hostname | port | gtid_port | weight | status | compression | max_connections | max_replication_lag | use_ssl | max_latency_ms | comment | mem_pointer | gtid_port | weight | status | compression | max_connections | max_replication_lag | use_ssl | max_latency_ms | comment | proxysql-1 | +--------------+-----------+------+-----------+--------+--------+-------------+-----------------+---------------------+---------+----------------+---------+-------------+-----------+--------+--------+-------------+-----------------+---------------------+---------+----------------+---------+ proxysql-1 | | 1 | 10.1.1.2 | 3306 | 0 | 900 | 0 | 0 | 1000 | 0 | 1 | 0 | | 0 | 0 | 900 | 0 | 0 | 1000 | 0 | 1 | 0 | | proxysql-1 | | 1 | 10.1.1.3 | 3306 | 0 | 500 | 0 | 0 | 1000 | 0 | 1 | 0 | | 0 | 0 | 500 | 0 | 0 | 1000 | 0 | 1 | 0 | | proxysql-1 | | 2 | 10.1.1.2 | 3306 | 0 | 1 | 0 | 0 | 1000 | 0 | 1 | 0 | | 0 | 0 | 1 | 0 | 0 | 1000 | 0 | 1 | 0 | | proxysql-1 | | 2 | 10.1.1.3 | 3306 | 0 | 1 | 0 | 0 | 1000 | 0 | 1 | 0 | | 0 | 0 | 1 | 0 | 0 | 1000 | 0 | 1 | 0 | | proxysql-1 | +--------------+-----------+------+-----------+--------+--------+-------------+-----------------+---------------------+---------+----------------+---------+-------------+-----------+--------+--------+-------------+-----------------+---------------------+---------+----------------+---------+ proxysql-1 | 2024-10-23 17:18:17 [INFO] Creating new server in HG 1 : 10.1.1.2:3306 , gtid_port=0, weight=900, status=0 proxysql-1 | 2024-10-23 17:18:17 [INFO] Creating new server in HG 1 : 10.1.1.3:3306 , gtid_port=0, weight=500, status=0 proxysql-1 | 2024-10-23 17:18:17 [INFO] Creating new server in HG 2 : 10.1.1.2:3306 , gtid_port=0, weight=1, status=0 proxysql-1 | 2024-10-23 17:18:17 [INFO] Creating new server in HG 2 : 10.1.1.3:3306 , gtid_port=0, weight=1, status=0 proxysql-1 | 2024-10-23 17:18:17 [INFO] New mysql_group_replication_hostgroups table proxysql-1 | 2024-10-23 17:18:17 [INFO] New mysql_galera_hostgroups table proxysql-1 | 2024-10-23 17:18:17 [INFO] New mysql_aws_aurora_hostgroups table proxysql-1 | 2024-10-23 17:18:17 [INFO] New mysql_hostgroup_attributes table proxysql-1 | 2024-10-23 17:18:17 [INFO] New mysql_servers_ssl_params table proxysql-1 | 2024-10-23 17:18:17 [INFO] Checksum for table mysql_servers_v2 is 0x9056858B796739E5 proxysql-1 | 2024-10-23 17:18:17 [INFO] Checksum for table mysql_replication_hostgroups is 0xC680B3A55720463B proxysql-1 | 2024-10-23 17:18:17 [INFO] New computed global checksum for 'mysql_servers_v2' is '0xF56946E87A6F861B' proxysql-1 | 2024-10-23 17:18:17 [INFO] Checksum for table mysql_servers is 0x9056858B796739E5 proxysql-1 | 2024-10-23 17:18:17 [INFO] Rebuilding 'Hostgroup_Manager_Mapping' due to checksums change - mysql_servers { old: 0x0, new: 0x796739E59056858B }, mysql_replication_hostgroups { old:0x0, new:0xC680B3A55720463B } proxysql-1 | 2024-10-23 17:18:17 [INFO] MySQL_HostGroups_Manager::commit() locked for 1ms proxysql-1 | 2024-10-23 17:18:17 [INFO] Computed checksum for 'LOAD PROXYSQL SERVERS TO RUNTIME' was '0x0000000000000000', with epoch '1729703897' proxysql-1 | Standard Query Processor rev. 2.0.6.0805 -- Query_Processor.cpp -- Fri Sep 20 15:51:19 2024 proxysql-1 | 2024-10-23 17:18:17 [INFO] Computed checksum for 'LOAD MYSQL QUERY RULES TO RUNTIME' was '0x61BE253E3448DAF4', with epoch '1729703897' proxysql-1 | In memory Standard Query Cache (SQC) rev. 1.2.0905 -- Query_Cache.cpp -- Fri Sep 20 15:51:19 2024 proxysql-1 | Standard MySQL Monitor (StdMyMon) rev. 2.0.1226 -- MySQL_Monitor.cpp -- Fri Sep 20 15:51:19 2024 proxysql-1 | Standard ProxySQL HTTP Server Handler rev. 1.4.1031 -- ProxySQL_HTTP_Server.cpp -- Fri Sep 20 15:51:19 2024 proxysql-1 | 2024-10-23 17:18:17 [INFO] For information about products and services visit: https://proxysql.com/ proxysql-1 | 2024-10-23 17:18:17 [INFO] For online documentation visit: https://proxysql.com/documentation/ proxysql-1 | 2024-10-23 17:18:17 [INFO] For support visit: https://proxysql.com/services/support/ proxysql-1 | 2024-10-23 17:18:17 [INFO] For consultancy visit: https://proxysql.com/services/consulting/ proxysql-1 | 2024-10-23 17:18:17 [INFO] read_only_action_v2() detected RO=0 on server 10.1.1.2:3306 for the first time after commit(), but no need to reconfigure proxysql-1 | 2024-10-23 17:18:17 [INFO] read_only_action_v2() detected RO=0 on server 10.1.1.3:3306 for the first time after commit(), but no need to reconfigure proxysql-1 | 2024-10-23 17:18:17 [INFO] Latest ProxySQL version available: 2.7.1-16-g2726c27 proxysql-1 | 2024-10-23 17:18:33 MySQL_Monitor.cpp:7384:monitor_read_only_process_ready_tasks(): [ERROR] Got error: mmsd 0x7f314fe09200 , MYSQL 0x7f314f000000 , FD 43 : Lost connection to server during query proxysql-1 | 2024-10-23 17:18:35 MySQL_Monitor.cpp:1632:monitor_read_only_thread(): [ERROR] Timeout on read_only check for 10.1.1.2:3306 after 0ms. Unable to create a connection. If the server is overload, increase mysql-monitor_connect_timeout. Error: timeout on creating new connection: Can't connect to server on '10.1.1.2' (115). proxysql-1 | 2024-10-23 17:18:36 MySQL_Monitor.cpp:1632:monitor_read_only_thread(): [ERROR] Timeout on read_only check for 10.1.1.2:3306 after 1ms. Unable to create a connection. If the server is overload, increase mysql-monitor_connect_timeout. Error: timeout on creating new connection: Can't connect to server on '10.1.1.2' (115). proxysql-1 | 2024-10-23 17:18:38 MySQL_Monitor.cpp:1632:monitor_read_only_thread(): [ERROR] Timeout on read_only check for 10.1.1.2:3306 after 1ms. Unable to create a connection. If the server is overload, increase mysql-monitor_connect_timeout. Error: timeout on creating new connection: Can't connect to server on '10.1.1.2' (115). proxysql-1 | 2024-10-23 17:18:38 MySQL_Monitor.cpp:1814:monitor_read_only_thread(): [ERROR] Server 10.1.1.2:3306 missed 3 read_only checks. Assuming read_only=1 proxysql-1 | 2024-10-23 17:18:38 [INFO] Server '10.1.1.2:3306' found with 'read_only=1', but not found as reader proxysql-1 | 2024-10-23 17:18:38 MySQL_HostGroups_Manager.cpp:7334:remove_HGM(): [WARNING] Removed server at address 0x7f3159e8b740, hostgroup 1, address 10.1.1.2 port 3306. Setting status OFFLINE HARD and immediately dropping all free connections. Used connections will be dropped when trying to use them proxysql-1 | 2024-10-23 17:18:38 [INFO] Regenerating table 'mysql_servers' due to actions on server '10.1.1.2:3306' proxysql-1 | 2024-10-23 17:18:38 [INFO] Dumping current MySQL Servers structures for hostgroup ALL proxysql-1 | HID: 1 , address: 10.1.1.3 , port: 3306 , gtid_port: 0 , weight: 500 , status: ONLINE , max_connections: 1000 , max_replication_lag: 0 , use_ssl: 1 , max_latency_ms: 0 , comment: proxysql-1 | HID: 2 , address: 10.1.1.2 , port: 3306 , gtid_port: 0 , weight: 1 , status: ONLINE , max_connections: 1000 , max_replication_lag: 0 , use_ssl: 1 , max_latency_ms: 0 , comment: proxysql-1 | HID: 2 , address: 10.1.1.3 , port: 3306 , gtid_port: 0 , weight: 1 , status: ONLINE , max_connections: 1000 , max_replication_lag: 0 , use_ssl: 1 , max_latency_ms: 0 , comment: proxysql-1 | 2024-10-23 17:18:38 [INFO] Dumping mysql_servers: ALL proxysql-1 | +-----+-----------+------+------+--------+--------+-----+-----------+---------+-----+---------+---------+-----------------+ proxysql-1 | | hid | hostname | port | gtid | weight | status | cmp | max_conns | max_lag | ssl | max_lat | comment | mem_pointer | proxysql-1 | +-----+-----------+------+------+--------+--------+-----+-----------+---------+-----+---------+---------+-----------------+ proxysql-1 | | 1 | 10.1.1.3 | 3306 | 0 | 500 | 0 | 0 | 1000 | 0 | 1 | 0 | | 139849938548736 | proxysql-1 | | 2 | 10.1.1.3 | 3306 | 0 | 1 | 0 | 0 | 1000 | 0 | 1 | 0 | | 139849938549120 | proxysql-1 | | 2 | 10.1.1.2 | 3306 | 0 | 1 | 0 | 0 | 1000 | 0 | 1 | 0 | | 139849938548928 | proxysql-1 | +-----+-----------+------+------+--------+--------+-----+-----------+---------+-----+---------+---------+-----------------+ proxysql-1 | 2024-10-23 17:18:38 [INFO] Checksum for table mysql_servers is 0x455B6D7DB20FD680 proxysql-1 | 2024-10-23 17:18:39 MySQL_Monitor.cpp:1632:monitor_read_only_thread(): [ERROR] Timeout on read_only check for 10.1.1.2:3306 after 1ms. Unable to create a connection. If the server is overload, increase mysql-monitor_connect_timeout. Error: timeout on creating new connection: Can't connect to server on '10.1.1.2' (115). proxysql-1 | 2024-10-23 17:18:39 MySQL_Monitor.cpp:1814:monitor_read_only_thread(): [ERROR] Server 10.1.1.2:3306 missed 3 read_only checks. Assuming read_only=1 proxysql-1 | 2024-10-23 17:18:41 MySQL_Monitor.cpp:1632:monitor_read_only_thread(): [ERROR] Timeout on read_only check for 10.1.1.2:3306 after 0ms. Unable to create a connection. If the server is overload, increase mysql-monitor_connect_timeout. Error: timeout on creating new connection: Can't connect to server on '10.1.1.2' (115). proxysql-1 | 2024-10-23 17:18:41 MySQL_Monitor.cpp:1814:monitor_read_only_thread(): [ERROR] Server 10.1.1.2:3306 missed 3 read_only checks. Assuming read_only=1 proxysql-1 | 2024-10-23 17:18:42 MySQL_Monitor.cpp:1632:monitor_read_only_thread(): [ERROR] Timeout on read_only check for 10.1.1.2:3306 after 1ms. Unable to create a connection. If the server is overload, increase mysql-monitor_connect_timeout. Error: timeout on creating new connection: Can't connect to server on '10.1.1.2' (115). proxysql-1 | 2024-10-23 17:18:42 MySQL_Monitor.cpp:1814:monitor_read_only_thread(): [ERROR] Server 10.1.1.2:3306 missed 3 read_only checks. Assuming read_only=1 proxysql-1 | 2024-10-23 17:18:44 MySQL_Monitor.cpp:1632:monitor_read_only_thread(): [ERROR] Timeout on read_only check for 10.1.1.2:3306 after 1ms. Unable to create a connection. If the server is overload, increase mysql-monitor_connect_timeout. Error: timeout on creating new connection: Can't connect to server on '10.1.1.2' (115). proxysql-1 | 2024-10-23 17:18:44 MySQL_Monitor.cpp:1814:monitor_read_only_thread(): [ERROR] Server 10.1.1.2:3306 missed 3 read_only checks. Assuming read_only=1 proxysql-1 | 2024-10-23 17:18:45 MySQL_Monitor.cpp:1632:monitor_read_only_thread(): [ERROR] Timeout on read_only check for 10.1.1.2:3306 after 1ms. Unable to create a connection. If the server is overload, increase mysql-monitor_connect_timeout. Error: timeout on creating new connection: Can't connect to server on '10.1.1.2' (115). proxysql-1 | 2024-10-23 17:18:45 MySQL_Monitor.cpp:1814:monitor_read_only_thread(): [ERROR] Server 10.1.1.2:3306 missed 3 read_only checks. Assuming read_only=1 proxysql-1 | 2024-10-23 17:18:47 MySQL_Monitor.cpp:1632:monitor_read_only_thread(): [ERROR] Timeout on read_only check for 10.1.1.2:3306 after 1ms. Unable to create a connection. If the server is overload, increase mysql-monitor_connect_timeout. Error: timeout on creating new connection: Can't connect to server on '10.1.1.2' (115). proxysql-1 | 2024-10-23 17:18:47 MySQL_Monitor.cpp:1814:monitor_read_only_thread(): [ERROR] Server 10.1.1.2:3306 missed 3 read_only checks. Assuming read_only=1 proxysql-1 | 2024-10-23 17:18:48 MySQL_Monitor.cpp:1632:monitor_read_only_thread(): [ERROR] Timeout on read_only check for 10.1.1.2:3306 after 0ms. Unable to create a connection. If the server is overload, increase mysql-monitor_connect_timeout. Error: timeout on creating new connection: Can't connect to server on '10.1.1.2' (115). proxysql-1 | 2024-10-23 17:18:48 MySQL_Monitor.cpp:1814:monitor_read_only_thread(): [ERROR] Server 10.1.1.2:3306 missed 3 read_only checks. Assuming read_only=1 proxysql-1 | 2024-10-23 17:18:50 MySQL_Monitor.cpp:1632:monitor_read_only_thread(): [ERROR] Timeout on read_only check for 10.1.1.2:3306 after 1ms. Unable to create a connection. If the server is overload, increase mysql-monitor_connect_timeout. Error: timeout on creating new connection: Can't connect to server on '10.1.1.2' (115). proxysql-1 | 2024-10-23 17:18:50 MySQL_Monitor.cpp:1814:monitor_read_only_thread(): [ERROR] Server 10.1.1.2:3306 missed 3 read_only checks. Assuming read_only=1 proxysql-1 | 2024-10-23 17:18:51 MySQL_Monitor.cpp:1632:monitor_read_only_thread(): [ERROR] Timeout on read_only check for 10.1.1.2:3306 after 1ms. Unable to create a connection. If the server is overload, increase mysql-monitor_connect_timeout. Error: timeout on creating new connection: Can't connect to server on '10.1.1.2' (115). proxysql-1 | 2024-10-23 17:18:51 MySQL_Monitor.cpp:1814:monitor_read_only_thread(): [ERROR] Server 10.1.1.2:3306 missed 3 read_only checks. Assuming read_only=1 proxysql-1 | 2024-10-23 17:18:53 MySQL_Monitor.cpp:1632:monitor_read_only_thread(): [ERROR] Timeout on read_only check for 10.1.1.2:3306 after 1ms. Unable to create a connection. If the server is overload, increase mysql-monitor_connect_timeout. Error: timeout on creating new connection: Can't connect to server on '10.1.1.2' (115). proxysql-1 | 2024-10-23 17:18:53 MySQL_Monitor.cpp:1814:monitor_read_only_thread(): [ERROR] Server 10.1.1.2:3306 missed 3 read_only checks. Assuming read_only=1 proxysql-1 | 2024-10-23 17:18:54 MySQL_Monitor.cpp:1632:monitor_read_only_thread(): [ERROR] Timeout on read_only check for 10.1.1.2:3306 after 0ms. Unable to create a connection. If the server is overload, increase mysql-monitor_connect_timeout. Error: timeout on creating new connection: Can't connect to server on '10.1.1.2' (115). proxysql-1 | 2024-10-23 17:18:54 MySQL_Monitor.cpp:1814:monitor_read_only_thread(): [ERROR] Server 10.1.1.2:3306 missed 3 read_only checks. Assuming read_only=1 proxysql-1 | 2024-10-23 17:18:56 MySQL_Monitor.cpp:1632:monitor_read_only_thread(): [ERROR] Timeout on read_only check for 10.1.1.2:3306 after 0ms. Unable to create a connection. If the server is overload, increase mysql-monitor_connect_timeout. Error: timeout on creating new connection: Can't connect to server on '10.1.1.2' (115). proxysql-1 | 2024-10-23 17:18:56 MySQL_Monitor.cpp:1814:monitor_read_only_thread(): [ERROR] Server 10.1.1.2:3306 missed 3 read_only checks. Assuming read_only=1 proxysql-1 | 2024-10-23 17:19:07 MySQL_Monitor.cpp:3177:monitor_ping(): [ERROR] Server 10.1.1.2:3306 missed 3 heartbeats, shunning it and killing all the connections. Disabling other checks until the node comes back online. proxysql-1 | 2024-10-23 17:30:38 [INFO] Server '10.1.1.2:3306' found with 'read_only=0', but not found as writer proxysql-1 | 2024-10-23 17:30:38 [INFO] Creating new server in HG 1 : 10.1.1.2:3306 , gtid_port=0, weight=1, status=0 proxysql-1 | 2024-10-23 17:30:38 [INFO] Regenerating table 'mysql_servers' due to actions on server '10.1.1.2:3306' proxysql-1 | 2024-10-23 17:30:38 [INFO] Dumping current MySQL Servers structures for hostgroup ALL proxysql-1 | HID: 1 , address: 10.1.1.3 , port: 3306 , gtid_port: 0 , weight: 500 , status: ONLINE , max_connections: 1000 , max_replication_lag: 0 , use_ssl: 1 , max_latency_ms: 0 , comment: proxysql-1 | HID: 1 , address: 10.1.1.2 , port: 3306 , gtid_port: 0 , weight: 1 , status: ONLINE , max_connections: 1000 , max_replication_lag: 0 , use_ssl: 1 , max_latency_ms: 0 , comment: proxysql-1 | HID: 2 , address: 10.1.1.2 , port: 3306 , gtid_port: 0 , weight: 1 , status: ONLINE , max_connections: 1000 , max_replication_lag: 0 , use_ssl: 1 , max_latency_ms: 0 , comment: proxysql-1 | HID: 2 , address: 10.1.1.3 , port: 3306 , gtid_port: 0 , weight: 1 , status: ONLINE , max_connections: 1000 , max_replication_lag: 0 , use_ssl: 1 , max_latency_ms: 0 , comment: proxysql-1 | 2024-10-23 17:30:38 [INFO] Dumping mysql_servers: ALL proxysql-1 | +-----+-----------+------+------+--------+--------+-----+-----------+---------+-----+---------+---------+-----------------+ proxysql-1 | | hid | hostname | port | gtid | weight | status | cmp | max_conns | max_lag | ssl | max_lat | comment | mem_pointer | proxysql-1 | +-----+-----------+------+------+--------+--------+-----+-----------+---------+-----+---------+---------+-----------------+ proxysql-1 | | 1 | 10.1.1.3 | 3306 | 0 | 500 | 0 | 0 | 1000 | 0 | 1 | 0 | | 139849938548736 | proxysql-1 | | 2 | 10.1.1.3 | 3306 | 0 | 1 | 0 | 0 | 1000 | 0 | 1 | 0 | | 139849938549120 | proxysql-1 | | 2 | 10.1.1.2 | 3306 | 0 | 1 | 0 | 0 | 1000 | 0 | 1 | 0 | | 139849938548928 | proxysql-1 | | 1 | 10.1.1.2 | 3306 | 0 | 1 | 0 | 0 | 1000 | 0 | 1 | 0 | | 139849770291200 | proxysql-1 | +-----+-----------+------+------+--------+--------+-----+-----------+---------+-----+---------+---------+-----------------+ proxysql-1 | 2024-10-23 17:30:38 [INFO] Checksum for table mysql_servers is 0xA13ED7B1C4DE79C8
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Hello,
I'm using proxysql docker image, version 2.7.1.
I'm starting mysql servers with different weight. One node goes down, once the node is up again, the server is re-added with a weight of 1.
Is there a way to retain the weight had before removal?
Full log below.
Many thanks,
Marius
The text was updated successfully, but these errors were encountered: