yaronbs wrote on Monday, December 05, 2016:
We are currently working on a large scale adaptation of OpenEMR. High availability concerns need to be addressed.
I was contemplating the use of Galera cluster over MariaDB, but have come accross several limitations, here are the main ones:
- All tables must have primary keys (I know some do not, but htis can be fixed)
- All tables must be based on innodb (almost all of them already are)
- the system must tolorate auto increment fields that may produce non-sequential values
- some unsupported explicit locking staements
More details can be found here:
https://mariadb.com/kb/en/mariadb/mariadb-galera-cluster-known-limitations.
There are more than a 100 tables with auto increment fields which appear many times in the codebase.
Does anyone have an idea whether or not these fields can tolerate non-sequential values?
Coming to the same issue from another angle, can anyone recommend a MySQL/MariaDB high availability solution that is relatively simple, up to date (such as Galera) and proven to work with OpenEMR in a production environment under a somewhat heavy load?
I was looking at GTID replication as an alternative that is less elegant but has less limitations that OpenEMR may stumble upon.
I would very much like to hear the community’s input on this issue.