[MDEV-21873] 10.2 to 10.3 upgrade doesn't remove semi-sync reference from mysql.plugin table Created: 2020-03-04 Updated: 2022-04-09 Resolved: 2022-03-25 |
|
| Status: | Closed |
| Project: | MariaDB Server |
| Component/s: | Plugins, Scripts & Clients |
| Affects Version/s: | 10.3, 10.4 |
| Fix Version/s: | 10.3.35, 10.4.25 |
| Type: | Bug | Priority: | Critical |
| Reporter: | Muhammad Irfan | Assignee: | Rucha Deodhar |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Issue Links: |
|
||||||||
| Description |
|
I noticed that upgrade from 10.2 -> 10.3 doesn't remove semi-sync reference from mysql.plugin table. As per documentation:
So, when Semisynchronous is already part of server then should be removed when upgrade is done to 10.3. It should be handled part of server or mysql_upgrade.
From here, I tried to upgrade from 10.2 to 10.3
As you can see reference to semi_sync plugins still present in mysql.plugin table after upgrade.
|
| Comments |
| Comment by Elena Stepanova [ 2020-03-07 ] |
|
serg, how do you want it to be handled? It's not this straightforward. Technically (even though it's unlikely), users can have their own custom plugins called the same way and installed in their instance, so just blindly removing them from the plugin table can cause unexpected effects. |
| Comment by Sergei Golubchik [ 2020-03-26 ] |
|
I suppose we can remove rpl_semi_sync_master and/or rpl_semi_sync_slave if they don't load anymore? Like, in mysql_upgrade check INFORMATION_SCHEMA.PLUGINS and if semisync plugins aren't there, delete them from mysql.plugin. |
| Comment by Rucha Deodhar [ 2022-03-25 ] |
|
Patch: https://github.com/MariaDB/server/commit/549a71e74b2fa494efcd79635a5db8af0d541f99 |
| Comment by Sergei Golubchik [ 2022-03-25 ] |
|
549a71e74b2f is ok to push |