Magento2: Magento 2.3.2 upgrade schema error with Percona XtraDB Cluster

[alchemyconsulting]

Preconditions (*)

1. Magento 2.3.2 (Upgrading from 2.2.9)
2. Centos 7.6.1810, PHP 7.1.30-3, Percona XtraDB Cluster 5.7.26-31

Steps to reproduce (*)

1. After doing composer update to magento 2.3.2, perform magento setup:upgrade
   2.

Expected result (*)

1. Expected clean upgrade of modules and database schema
   2.

Actual result (*)

1.

[root@xxx /xxx/html]# bin/magento setup:upgrade
Cache cleared successfully
File system cleanup:
/xxx/html/generated/code/Composer
/xxx/html/generated/code/MageWorx
/xxx/html/generated/code/Magento
/xxx/html/generated/code/Mirasvit
/xxx/html/generated/code/Symfony
The directory '/xxx/html/generated/metadata/' doesn't exist - skipping cleanup
/xxx/html/pub/static/_cache
/xxx/html/pub/static/adminhtml
/xxx/html/pub/static/deployed_version.txt
/xxx/html/pub/static/frontend
/xxx/html/var/view_preprocessed/pub
Updating modules:
Schema creation/updates:
SQLSTATE[HY000]: General error: 1105 Percona-XtraDB-Cluster prohibits changing storage engine of a table (xxx.catalog_product_index_price_cfg_opt_agr_tmp) from transactional to non-transactional with pxc_strict_mode = ENFORCING or MASTER, query was: ALTER TABLE `catalog_product_index_price_cfg_opt_agr_tmp` ENGINE='memory'

2.

[m2-assistant[bot]]

Hi @alchemyconsulting. Thank you for your report.
To help us process this issue please make sure that you provided the following information:

• [ ] Summary of the issue
• [ ] Information on your environment
• [ ] Steps to reproduce
• [ ] Expected and actual results

Please make sure that the issue is reproducible on the vanilla Magento instance following Steps to reproduce. To deploy vanilla Magento instance on our environment, please, add a comment to the issue:

@magento give me 2.3-develop instance - upcoming 2.3.x release

For more details, please, review the Magento Contributor Assistant documentation.

@alchemyconsulting do you confirm that you were able to reproduce the issue on vanilla Magento instance following steps to reproduce?

• [ ] yes
• [ ] no

---

• Join Magento Community Engineering Slack and ask your questions in #github channel.

[m2-assistant[bot]]

Hi @engcom-Charlie. Thank you for working on this issue.
In order to make sure that issue has enough information and ready for development, please read and check the following instruction: :point_down:

• [ ] 1. Verify that issue has all the required information. (Preconditions, Steps to reproduce, Expected result, Actual result).
  Details

  If the issue has a valid description, the label Issue: Format is valid will be added to the issue automatically. Please, edit issue description if needed, until label Issue: Format is valid appears.

• [ ] 2. Verify that issue has a meaningful description and provides enough information to reproduce the issue. If the report is valid, add Issue: Clear Description label to the issue by yourself.

• [ ] 3. Add Component: XXXXX label(s) to the ticket, indicating the components it may be related to.

• [ ] 4. Verify that the issue is reproducible on 2.3-develop branch

  Details

  - Add the comment @magento give me 2.3-develop instance to deploy test instance on Magento infrastructure.
  - If the issue is reproducible on 2.3-develop branch, please, add the label Reproduced on 2.3.x.
  - If the issue is not reproducible, add your comment that issue is not reproducible and close the issue and _stop verification process here_!

• [ ] 5. Add label Issue: Confirmed once verification is complete.

• [ ] 6. Make sure that automatic system confirms that report has been added to the backlog.

[engcom-Charlie]

Hello @alchemyconsulting
We can not reproduce this issue follow steps that you provide.
Please refer to the Community Forums or the Magento Stack Exchange, for advice or general discussion about this issue.

[opensourcelib]

Maybe I'm little late about this issue but just in case someone gets this problem in the future this will be "helpful".
According to Galera Cluster this issued is part of the Known Limitation to be able to run that query you need to change the value of the variable "pxc_strict_mode" to DISABLED or PERMISSIVE for more details please read Percona website

Also you can read MariaDB Explanation I know you are using Percona cluster but MariaDB use the same library for its cluster so that explanation is helpful

in conclusion you can execute the following query in a running cluster:
mysql> SET GLOBAL pxc_strict_mode=PERMISSIVE;

[alchemyconsulting]

@opensourcelib - Changing the PXC mode to permissive is generally a Bad Idea (TM) - it turns off the validation and integrity checks that are there for a reason, when you have semi-synchronous replication.
In this particular case I think it means that the relevant table will then not be replicated, so if you then use another node you may have inconsistent/unreliable data.