Use docker official image, Set up a galera cluster with 3 nodes

If you're wondering about the error message its because Codership are belligerent about reusing system error codes that are totally stupid and highly misleading in the context of galera errors and refuse to fix them (https://github.com/codership/galera/pull/109) or even document them.

Not sure if it helps but this galera test https://github.com/MariaDB/server/blob/10.5/mysql-test/suite/galera/t/galera_gcs_fragment.test#L57 returns ER_ERROR_DURING_COMMIT which likely occured in your production scenario.

Rather off topic for you bug report, as you are using the docker official image and galera would you be able to help out reviewing https://github.com/MariaDB/mariadb-docker/pull/377 and creating a new issue on what is needed to make the official image easier to use with galera?

I google the error and find it in the test case(https://github.com/MariaDB/server/blob/a3099a3b4a394da360b5c1e7ae6dc985ae2f7f2f/mysql-test/suite/galera/r/galera_gcs_fragment.result)

Yes, that is the expected test result output from the test case that I linked to. ER_ERROR_DURING_COMMIT in full is the error you received.

The test case shows a restart of the destination node at the point at which the galera replication of the data, in your case sql, is being sent.

Can you attach the container logs for each 3 node?

Are all the galera nodes in your cluster stable and joined at the time that you sql? Is this a repeatable test?

Are other nodes modifying the data/tables that corresponds to your sql?

Does a smaller test case generate the same error?

Is your sql file a simple mysqldump? Can you identify the SQL statement that caused the error?

Do you have any special configuration of mariadb in .cnf files?

thx, I will try to repearable it.