This the case where threre are theree Ejbca appliances. These appliances are using MariaDB galera cluster each other. Each database are located inside the appliance. I wish to know the behavior about high availability of Ejbca galera cluster.
The questions are as follows:
1) Does Ejbca web application connect to Mariadb cluster through virtual IP similar as occurs in keepalived?
2) Are the incoming packets to database cluster balanced into three appliances?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi,
When using a MarieDB Glera cluster with say three nodes, each EJBCA node typically connects to it's "own" MariaDB node, making the EJBCA+MariaDB "one package" for each node.
There is nothing preventing you from running a Galera cluster of your own, with a VIP in-front of course, that is also a valid deployment model (but not how it works in the Appliance).
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi
This the case where threre are theree Ejbca appliances. These appliances are using MariaDB galera cluster each other. Each database are located inside the appliance. I wish to know the behavior about high availability of Ejbca galera cluster.
The questions are as follows:
1) Does Ejbca web application connect to Mariadb cluster through virtual IP similar as occurs in keepalived?
2) Are the incoming packets to database cluster balanced into three appliances?
Hi,
When using a MarieDB Glera cluster with say three nodes, each EJBCA node typically connects to it's "own" MariaDB node, making the EJBCA+MariaDB "one package" for each node.
There is nothing preventing you from running a Galera cluster of your own, with a VIP in-front of course, that is also a valid deployment model (but not how it works in the Appliance).