Known Issues When Handling InnoDB Cluster using MySQL Shell.
(Doc ID 2263295.1)
Last updated on MARCH 27, 2020
Applies to:MySQL Server - Version 5.6 and later
Information in this document applies to any platform.
Described some of known issues that can affect the creation and handling of a InnoDB Cluster using MySQL Shell
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document
|1- Creating a InnoDB cluster an error is displayed preventing the cluster to be created.|
|2 - Error related with passwords after creating a InnoDB Cluster|
|3 - Access denied error, preventing the cluster to be created|
|4 - When running the command "dba.rebootClusterFromCompleteOutage" the InnoDb Cluster group name is not maintained|
|5 - When MySQL Shell Admin API commands fail with "Missing port number (ArgumentError)"|
|6 - After a restoring a Node it cannot join the cluster with error: "Non-compatible tables found in database. (RuntimeError)"|
|7 - After issuing dba.rebootClusterFromCompleteOutage the MySQL Shell becomes stuck and "[Note] Plugin group_replication reported: 'cli_err 2'" in the MySQL Instance error log|