Skip to content

Latest commit

 

History

History
20 lines (13 loc) · 1.72 KB

HA.md

File metadata and controls

20 lines (13 loc) · 1.72 KB
Raw

High availability

This operator supports the following High Availability modes:

  • Single master HA via SemiSync Replication: The primary node allows both reads and writes, while secondary nodes only allow reads.
  • Multi master HA via Galera: All nodes support reads and writes, but it is recommended to perform writes in a single primary for preventing deadlocks.

Kubernetes Services

In order to address nodes, mariadb-operator provides you with the following Kubernetes Services:

  • <mariadb-name>: To be used for read requests. It will point to all nodes.
  • <mariadb-name>-primary: To be used for write requests. It will point to a single node, the primary.
  • <mariadb-name>-secondary: To be used for read requests. It will point to all nodes, except the primary.

Whenever the primary changes, either by the user or by the operator, both the <mariadb-name>-primary and <mariadb-name>-secondary Services will be automatically updated by the operator to address the right nodes.

The primary may be manually changed by the user at any point by updating the spec.[replication|galera].primary.podIndex field. Alternatively, automatic primary failover can be enabled by setting spec.[replication|galera].primary.automaticFailover, which will make the operator to switch primary whenever the primary Pod goes down.

MaxScale

While Kubernetes Services can be utilized to dynamically address primary and secondary instances, the most robust high availability configuration we recommend relies on MaxScale. Please refer to MaxScale docs for further details.