Skip to content

v2.0.5
Compare
Choose a tag to compare
@kennt-percona kennt-percona released this 12 Aug 23:17
v2.0.5
3f4d966
This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
GPG key ID: 4AEE18F83AFDEB23
Expired
Learn about vigilant mode.

Release date: August 12, 2019

Improvements

  • PSQLADM-49 : Create rules for --syncusers
    When running with --syncusers or --sync-multi-cluster-users, the --add-query-rule option can now be specified to add the singlewriter query rules for the new users.

  • PSQLADM-51 : Update mysql-server_version variable
    A command --update-mysql-version was added to set the mysql-server_version global variable in ProxySQL. This will take the version from a node in the cluster and set it in ProxySQL.

Bug Fixes

  • PSQLADM-190 : remove-all-servers option doesn't work on enable
    When running with proxysql-cluster, the galera hostgroups information is not being replicated, which leads us to fail when running --enable on a different ProxySQL node. The --force option was added for --enable, which will cause the enable to ignore any errors and always configure the cluster.

  • PSQLADM-199 query-rules removed during proxysql-cluster creation with PXC operator
    When using the PXC operator for Kubernetes and creating a proxysql-cluster, the query rules were being removed. Modified the code to merge the query rules (rather than deleting and recreating). If --force is specified, than a warning is issued if there are preexisting rules are found, otherwise an error is issued.
    Also added the --disable-updates option, to ensure that proxysql cluster updates do not interfere with the current command.

  • PSQLADM-200 users are not being created with --syncusers with PXC operator
    When using the PXC operator for Kubernetes, the ---syncusers command would run, but would leave an empty mysql users table. The fix for PSQLADM-199, to use --disable-updates also applies here.

Assets 2
Loading