Bug #111496 Clone plugin does not have compatibility check for different storage engine
Submitted: 20 Jun 2023 15:32 Modified: 21 Jun 2023 13:51
Reporter: Chun Ni Email Updates:
Status: Verified Impact on me:
None 
Category:MySQL Server: Clone Plugin Severity:S4 (Feature request)
Version:8.0 OS:Any
Assigned to: CPU Architecture:Any

[20 Jun 2023 15:32] Chun Ni 
Description:
When running clone command between two instances that have different numbers of storage engine, the donor will crash.

For instance, in our case, we use innoDB and rocksDB as two storage engines when running clone commands.

Client has Rocksdb and innodb, donor only has Innodb: donor will crash due to m_hton of rocksdb is null. Vice verse, it will also crash.

How to repeat:
Load innodb in the client, Load innodb and rocksdb in the donor, run clone command.

Load innodb and rocksdb in the client, Load innodb in the client, run clone command.

Suggested fix:
Add check for the compatibility of se in client and donor
[21 Jun 2023 8:59] Laurynas Biveinis 
Part of https://bugs.mysql.com/bug.php?id=109926 (Clone plugin does not support transactional SEs other than InnoDB)
[21 Jun 2023 12:22] MySQL Verification Team 
Hi Mr. Ni,

Thank you, very much, for your feature request.

MySQL does not support RocksDB, nor does it supports cloning with transactional engines.

Hence, your report is a duplicate of the following feature request:

https://bugs.mysql.com/bug.php?id=109926

When the above one is implemented, this feature will be available too.

Version 8.0 is feature frozen, so you should follow 8.1 development, when it becomes public.

Duplicate.
[21 Jun 2023 12:45] Laurynas Biveinis 
This is not a duplicate of bug 109926 because this is only one small part of bug 109926
[21 Jun 2023 12:54] MySQL Verification Team 
HI,

That is true.

However, implementing the original feature request would solve this one as well.

Also, we do not support third party storage engines, so the only way of resolving this problem is a development of the SE Plugin that supports transactions.

By our criteria, a repot is a duplicate, if the original bug / feature request solves the new report as well.

Also, having a number of duplicates increases the weight of the original feature request.
[21 Jun 2023 13:51] MySQL Verification Team 
Hi,

This feature request is now verified, since it has to be considered as a separate issue.