ProxySQL 2.0.1 Native galera support: Flag Active is not correctly working

[Tusamarco]

This is the place for paid support and community users to report a reproducible bug in ProxySQL, suggest enhancements or make feature requests. This also includes documentation errors and/or missing documentation.

• Remember, this is the place for fixing and improving ProxySQL rather than the place to get free support.
• If you do not have a paid support contract please try https://groups.google.com/forum/#!forum/proxysql. Due to the high volume of requests, we are unable to always provide timely support for community users.

If you are submitting a reproducible bug report, please provide:
[ ] A clear description of your issue
[ ] The version of OS and ProxySQL
[ ] Every step to reproduce the issue
[ ] The error log
[ ] If it is a crashing bug, please check here: https://github.com/sysown/proxysql/wiki/How-to-report-a-crash-bug

Please use markdown to format code or SQL: https://guides.github.com/features/mastering-markdown/

Thank you!

[Tusamarco]

ProxySQL version v2.0.1-0-gac2e710, codename Truls
Also if the Active flag is =0. ProxySQL is managing the nodes as if the rule in set to active.

*************************** 1. row ***************************
       writer_hostgroup: 100
backup_writer_hostgroup: 102
       reader_hostgroup: 101
      offline_hostgroup: 9101
                 active: 0
            max_writers: 1
  writer_is_also_reader: 1
max_transactions_behind: 16
                comment: NULL
1 row in set (0.01 sec)

mysql> select * from runtime_mysql_servers where hostgroup_id in (100,101,102);
+--------------+---------------+------+-----------+--------+--------+-------------+-----------------+---------------------+---------+----------------+---------+
| hostgroup_id | hostname      | port | gtid_port | status | weight | compression | max_connections | max_replication_lag | use_ssl | max_latency_ms | comment |
+--------------+---------------+------+-----------+--------+--------+-------------+-----------------+---------------------+---------+----------------+---------+
| 100          | 192.168.1.205 | 3306 | 0         | ONLINE | 10000  | 0           | 1000            | 0                   | 0       | 0              |         |
| 101          | 192.168.1.205 | 3306 | 0         | ONLINE | 10000  | 0           | 1000            | 0                   | 0       | 0              |         |
| 101          | 192.168.1.21  | 3306 | 0         | ONLINE | 100    | 0           | 1000            | 0                   | 0       | 0              |         |
| 101          | 192.168.1.231 | 3306 | 0         | ONLINE | 100    | 0           | 1000            | 0                   | 0       | 0              |         |
| 102          | 192.168.1.21  | 3306 | 0         | ONLINE | 100    | 0           | 1000            | 0                   | 0       | 0              |         |
| 102          | 192.168.1.231 | 3306 | 0         | ONLINE | 100    | 0           | 1000            | 0                   | 0       | 0              |         |
+--------------+---------------+------+-----------+--------+--------+-------------+-----------------+---------------------+---------+----------------+---------+
6 rows in set (0.01 sec)

mysql> select * from runtime_mysql_servers where hostgroup_id in (100,101,102,9101);
+--------------+---------------+------+-----------+--------+--------+-------------+-----------------+---------------------+---------+----------------+---------+
| hostgroup_id | hostname      | port | gtid_port | status | weight | compression | max_connections | max_replication_lag | use_ssl | max_latency_ms | comment |
+--------------+---------------+------+-----------+--------+--------+-------------+-----------------+---------------------+---------+----------------+---------+
| 100          | 192.168.1.231 | 3306 | 0         | ONLINE | 100    | 0           | 1000            | 0                   | 0       | 0              |         |
| 101          | 192.168.1.21  | 3306 | 0         | ONLINE | 100    | 0           | 1000            | 0                   | 0       | 0              |         |
| 101          | 192.168.1.231 | 3306 | 0         | ONLINE | 100    | 0           | 1000            | 0                   | 0       | 0              |         |
| 102          | 192.168.1.21  | 3306 | 0         | ONLINE | 100    | 0           | 1000            | 0                   | 0       | 0              |         |
| 9101         | 192.168.1.205 | 3306 | 0         | ONLINE | 10000  | 0           | 1000            | 0                   | 0       | 0              |         |
+--------------+---------------+------+-----------+--------+--------+-------------+-----------------+---------------------+---------+----------------+---------+
5 rows in set (0.01 sec)```

I do not think there is need of more info but in the case let me know

[Tusamarco]

@renecannao @pondix can u please check/validate the issue?

[pondix]

Ack, its in the queue.... will check it out and let you know

[fenice2]

@pondix has any progress been made on this issue?

[renecannao]

Closing. #2443 fixed this