DirectAdmin & MariaDB Galera Cluster

RuudNoBears

New member
Joined
Aug 24, 2018
Messages
4
Hi there,

We are using DirectAdmin on 3 different webservers and setup MariaDB to work as a Galera Cluster.

At this moment we are running into one problem. When we import a back-up the database users are inserted with a simple INSERT INTO query. Because the mysql.user table is MyISAM these inserts are not automaticly synced across the cluster because it only supports InnoDB.

The only way to sync the users table is to create users with a DDL operation like 'CREATE USER'.

Is it possible to change the DA backup to use create user instead of insert into?
 
Not actually DA's fault, but I agree that it sucks with galera clusters. Would be nice if there was an option to generate 'create user' statements automatically. +1
 
Please create a ticket. This will require some fiddling, as it needs to be sorted for cases where the account already exists, and other things like plain-text pass vs hashed for the restore.
DA actually uses "UPDATE", as it handles both non-existent and existing User, so more checks would be needed...eg: which DDL is used to update privileges, access hosts, etc. (we can go through all that in the ticket)
Either way, its shouldn't be too "hard", just a lot of rewrites to ensure it's working correctly for all cases.

John
 
I'll leave the ticket for RuudNoBears as he needs it more than I, but thanks, John, for considering it!
 
Thanks

Please create a ticket. This will require some fiddling, as it needs to be sorted for cases where the account already exists, and other things like plain-text pass vs hashed for the restore.
DA actually uses "UPDATE", as it handles both non-existent and existing User, so more checks would be needed...eg: which DDL is used to update privileges, access hosts, etc. (we can go through all that in the ticket)
Either way, its shouldn't be too "hard", just a lot of rewrites to ensure it's working correctly for all cases.

John

Nice! Thanks for the reply, will create a ticket asap :)
 
Thanks

Please create a ticket. This will require some fiddling, as it needs to be sorted for cases where the account already exists, and other things like plain-text pass vs hashed for the restore.
DA actually uses "UPDATE", as it handles both non-existent and existing User, so more checks would be needed...eg: which DDL is used to update privileges, access hosts, etc. (we can go through all that in the ticket)
Either way, its shouldn't be too "hard", just a lot of rewrites to ensure it's working correctly for all cases.

John

He John, good to hear and thanks for the reply! Will create a ticket asap.
 
Back
Top