Bug #104299 Flexibilise the clone_plugin to not force plugins to match on recipient/donor

• Submitted: 13 Jul 2021 15:41
• Modified: 14 Jul 2021 5:08
• Reporter: Simon Mudd (OCA)
• Status: Verified
• Category: MySQL Server: Clone Plugin
• Severity: S4 (Feature request)
• Version: 8.0.25
• OS: Any
• CPU Architecture: Any
• Tags: clone_plugin, flexibility, plugin_mismatch

[13 Jul 2021 15:41] Simon Mudd

Description:
When attempting native cloning we may see this error:

3870, 'Clone Donor plugin <plugin_name> is not active in Recipient.'

This is because the native clone plugin is overly paranoid.

I have some plugins installed locally on the server and they may not be needed on the recipient.  These plugins do not modify/affect data in on server and I know that.  Forcing me to install them on the recipient is not helpful or ideal.

How to repeat:
Configure the recipient and donor with different plugins (in /etc/my.cnf) especially the recipient with less plugins than the donor.

See that you get this error message with the missing plugin.

Suggested fix:
Provide a list of plugins to exclude from these checks allowing the cloning to go ahead despite them being missing.

e.g.

something like: clone_exclude_donor_plugin_match_list = my_special_plugin_to_exclude

I'm not 100% sure if once the cloning is complete if I'll need to exclude the plugin from those being auto-loaded as they may not be there, but you get the idea.

[14 Jul 2021 5:08] MySQL Verification Team

Hello Simon,

Thank you for the feature request!

regards,
Umesh