The Keyring Proxy Bridge Plugin •The clone plugin does not support cloning of binary logs. •The clone plugin only clones data stored in  InnoDB . Other storage engine data is not cloned.  MyISAM and  CSV  tables stored in any schema including the  sys  schema are cloned as empty tables. •Connecting to the donor MySQL server instance through MySQL Router is not supported. •Local cloning operations do not support cloning of general tablespaces that were created with an absolute path. A cloned tablespace file with the same path as the source tablespace file would cause a conflict. •Namespace and lock names must be non- NULL , nonempty, and have a maximum length of 64 characters. A namespace or lock name specified as  NULL , the empty string, or a string longer than 64 characters results in an  ER_LOCKING_SERVICE_WRONG_NAME  error. •A lock mode is either read or write. Read locks are shared: If a session has a read lock on a given lock identifier, other sessions can acquire a read lock on the same identifier. Write locks are exclusive: If a session has a write lock on a given lock identifier, other sessions cannot acquire a read or write lock on the same identifier. •Locks are identified by the combination of namespace and lock name. The namespace enables different applications to use the same lock names without colliding by creating locks in separate namespaces. For example, if applications A and B use namespaces of  ns1  and  ns2 , respectively, each application can use lock names  lock1  and  lock2  without interfering with the other application. •Locks have three attributes: Lock namespace, lock name, and lock mode: 1135 The locking interface has these characteristics: For general information about plugin services, see Section 5.6.9, “MySQL Plugin Services” . For general information about loadable functions, see Adding a Loadable Function. MySQL server plugins have access to server “plugin services.”  The plugin services interface complements the plugin API by exposing server functionality that plugins can call. For developer information about writing plugin services, see MySQL Services for Plugins. The following sections describe plugin services available at the SQL and C-language levels. daemon_keyring_proxy_plugin  is built in and nothing need be done to install or enable it. MySQL Keyring originally implemented keystore capabilities using server plugins, but began transitioning to use the component infrastructure in MySQL 8.0.24. The transition includes revising the underlying implementation of keyring plugins use the component infrastructure. This is facilitated using the plugin named  daemon_keyring_proxy_plugin  that acts as a bridge between the plugin and component service APIs, and enables keyring plugins to continue to be used with no change to user-visible characteristics. 5.6.8 The Keyring Proxy Bridge Plugin 5.6.9 MySQL Plugin Services 5.6.9.1 The Locking Service •As a C language interface, callable as a plugin service from server plugins or loadable functions. •At the SQL level, as a set of loadable functions that each map onto calls to the service routines. MySQL distributions provide a locking interface that is accessible at two levels: