Issues

percona-xtrabackup-80-8.0.3-rc1.el7.x86_64: prepare fails on 8.0.13 backup

percona-xtrabackup-80-8.0.1-2.alpha2.el7.x86_64 failure

pt-online-schema-change exit status(return code) is 0 even if it does NOT succeed

Every next run of pt-online-schema-change will result in an error and create a new table that won’t be cleaned up

pt-online-schema-change should not resume a job with empty boundaries

pt-online-schema-change needs options to better adjust to the workload to avoid overloading

Implement additional logic for replica checking

pt-online-schema-change creates huge transactions on tables with big rows

Add support for InnoDB Cluster/Group Replication in pt-online-schema-change

resume pt-online-schema-change if it's interrupted

Couple of thoughts with docker pmm image 2.24.0

Error 3159 (HY000): Connections using insecure transport are prohibited while --require_secure_transport=ON

RestartReplicationQuick called even from Orchestrator cluster where recovery has been globally disabled

Orchestrator RestartReplicationQuick fails with Error 1065 (query was empty)

provide in debug/metrics endpoint metrics on http responses and api endpoint responses

Provide a way to be able to embed links to MySQL servers in external systems.

Provide an exclusion list instead of a Recover list for master / intermediate master recovery actions

Provide better visibility of ongoing failover handling in orchestrator

Support MySQL 8.4 and 9.X in orchestrator

Improve orchestrator performance when multiple systems fail at the same time

Orchestrator should handle tagged GTIDs

Orchestrator exposes MySQLOrchestratorPassword variable

Orchestrator panic: runtime error: invalid memory address or nil pointer dereference

Fix for DISTMYSQL-243 can lead to Orchestrator hitting duplicate keys

Orchestrator - ERROR Unable to determine cluster name. clusterHint=XXXX

orchestrator semi-sync configuration indication in GUI is wrong/misleading - please correct

Fix 'driver: bad connection' errors seen in orchestrator

Orchestrator uses inefficient subquery in REPLACE to update cluster aliases

Orchestrator log fills with "WARNING: NamedStopwatch.Stop("instance") IsRunning is false"

Orchestrator GUI messages should optionally contain the name of the orchestratorapp generating the message

Handle max_allowed_packet setting being incorrect in orchestrator

Use MySQL driver's SetConnMaxLifetime for topology connections to improve handling of firewall issues

Orchestrator: --version option does not return easily understandable version number

Add max execution time query hint to prevent GR lockup blocking orchestrator

Fix error management during relocation of replicas.

Orchestrator should have a definable black list of usernames to prevent some servers being considered as MySQL servers.

Orchestrator generates a lot of "Connection refused" log error when MySQL is not reachable/available