GR consistency: Unable to parse unknown SET query from client <ip:port>. Setting lock_hostgroup.

[GregorFritzE2]

reproducible bug for ProxySQL.

• A clear description of the issue
  We have recently started using ProxySQL to balance access to our DB cluster however some of the apps accessing the cluster should be able to write faster and not use consistency level 'AFTER' but level 'EVENTUAL' instead.
• ProxySQL version: proxysql/proxysql:2.3.2
• OS version: official ProxySQL image running in Docker
• The steps to reproduce the issue

• Execute SET time_zone='UTC', @@SESSION.group_replication_consistency='EVENTUAL';
  • Time zone is set
  • Group replication consistency is not, message Unable to parse unknown SET query from client <ip:port>. Setting lock_hostgroup. is logged.
  • Can suppress error by adding rule INSERT INTO mysql_query_rules (rule_id,active,match_digest,apply,multiplex) VALUES (3,1,'group_replication_consistency=',1,1); (not a solution since the statement is not executed on the cluster)
  • Makes no difference if SET statements are executed together or separate.

• The full ProxySQL error log (default location: /var/lib/proxysql/proxysql.log)
  proxysql.log

[renecannao]

Thank you for the report.

[GregorFritzE2]

Is there any update on this issue? Or any intention of supporting these kinds of statements?

[renecannao]

With the refactoring work done in PR #3702 it should be easy to also add group_replication_consistency . We should plan to include it in version 2.4

[GregorFritzE2]

With the refactoring work done in PR #3702 it should be easy to also add group_replication_consistency . We should plan to include it in version 2.4

Thanks for the reply!