Work with MySQL group replication

[itsmdev]

Error log:

2022-08-24 02:14:35,802 ERROR [c.c.u.d.Merovingian2] (main:null) (logid:) cleanupForServer:Exception:The table does not comply with the requirements by an external plugin.
2022-08-24 02:14:35,909 ERROR [c.c.u.d.Merovingian2] (main:null) (logid:) cleanupForServer:Exception:cleanupForServer:Exception:The table does not comply with the requirements by an external plugin.

seem caused by op_lock and op_nwgrp_work use MEMORY engine:

| def           | cloud              | op_lock                                              | MEMORY             |
| def           | cloud              | op_nwgrp_work                                        | MEMORY             |
+---------------+--------------------+------------------------------------------------------+--------------------+

any solution?

in ./engine/schema/src/main/resources/META-INF/db/schema-490to4910.sql:, engine will be set to innodb：

ALTER TABLE cloud.op_nwgrp_work ENGINE=INNODB;

So, can I use InnoDB from the start？

ISSUE TYPE

• Bug Report

COMPONENT NAME

CLOUDSTACK VERSION

4.16.1.0

CONFIGURATION

OS / ENVIRONMENT

SUMMARY

STEPS TO REPRODUCE

EXPECTED RESULTS

ACTUAL RESULTS

[boring-cyborg]

Thanks for opening your first issue here! Be sure to follow the issue template!

[yadvr]

@itsmdev thanks for reporting, I think they all should be INNODB unless there is any reason not to. Can you check latest main or 4.17 branch incase this is already fixed those cc @nvazquez if you remember we fixed them?

[itsmdev]

@rohityadavcloud

cloudstack/setup/db/create-schema.sql

Line 401 in c581181

) ENGINE=Memory DEFAULT CHARSET=utf8;

cloudstack/setup/db/create-schema.sql

Line 1796 in c581181

) ENGINE=MEMORY DEFAULT CHARSET=utf8;

[DaanHoogland]

according to https://github.com/apache/cloudstack/blob/4.17/engine/schema/src/main/resources/META-INF/db/schema-490to4910.sql#L30-L31 this has long been changed and will be automatically be updated on every installation after 4.9

Not sure what you require. does installation fail? or upgrade?

[DaanHoogland]

@itsmdev I am closing this issue. If you feel this is invalid please reopen or create a new one

[Revellski]

This can be replicated on new install, when bootstrapping with cloudstack-setup-databases. I guess the script uses an older schema which is expected to be upgraded during the first run. However, CloudStack fails to start due to the error above.

[Demonium]

Hello,
I just had the same issue on version 4.20 after a fresh installation...
I have executed the lines below to correct the issue
ALTER TABLE cloud.op_lock ENGINE=INNODB; ALTER TABLE cloud.op_nwgrp_work ENGINE=INNODB;

[DaanHoogland]

so there are two issues here that both would not lead to problems in isolation:

1. the default table type (ENGINE) should be set to innodb. this can be documented as a prerequisite setup for mysql
2. the addition of new tables shouls always speficify an engine. this is hard to enforce but a retroaction on existing tables can be done (i.e. a “bug”fix)
   I suggest we do both. What do you think @weizhouapache @rohityadavcloud @vishesh92 others?

[Demonium]

Hello,
I have setup again cloudstack on a fresh database installation without setup innodb cluster and it's work perfectly at first time I don't know if it's relevant for you ?