# Database clustering with Ignition

**URL:** <https://forum.inductiveautomation.com/t/database-clustering-with-ignition/41146>\
**Category:** Ignition\
**Created:** [December 2, 2020, 5:08pm UTC](https://forum.inductiveautomation.com/t/database-clustering-with-ignition/41146 "2020-12-02T17:08:59Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![AlThePal](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/althepal/32/3603_2.png) [@AlThePal](https://forum.inductiveautomation.com/u/AlThePal)\
**Post date:** [December 2, 2020, 5:08pm UTC](https://forum.inductiveautomation.com/t/database-clustering-with-ignition/41146/1 "2020-12-02T17:08:59Z")

</div>

Does anyone have experience of using database clustering with Ignition? We’re thinking of using MariaDB Galera Cluster.

---

<div class="post-metadata">

**Author:** ![Kevin.Herron](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/kevin.herron/32/7259_2.png) [@Kevin.Herron](https://forum.inductiveautomation.com/u/Kevin.Herron)\
**Post date:** [December 2, 2020, 6:27pm UTC](https://forum.inductiveautomation.com/t/database-clustering-with-ignition/41146/2 "2020-12-02T18:27:23Z")

</div>

Anecdotally, I recall a customer trying to use MySQL Fabric for clustering/HA and it being a complete cluster f&\*^. YMMV

---

<div class="post-metadata">

**Author:** ![mazeyrat](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/mazeyrat/32/10955_2.png) [@mazeyrat](https://forum.inductiveautomation.com/u/mazeyrat)\
**Post date:** [December 2, 2020, 7:12pm UTC](https://forum.inductiveautomation.com/t/database-clustering-with-ignition/41146/3 "2020-12-02T19:12:09Z")

</div>

We use MySQL innodb cluster.

[https://dev.mysql.com/doc/refman/8.0/en/mysql-innodb-cluster-introduction.html](https://dev.mysql.com/doc/refman/8.0/en/mysql-innodb-cluster-introduction.html)

You need at least 3 nodes.  
All tables must have primary Key  
So you have to add some pk auto increment for one or 2 igniton tag historian table.

---

<div class="post-metadata">

**Author:** ![brandon1](https://avatars.discourse-cdn.com/v4/letter/b/ea666f/32.png) [@brandon1](https://forum.inductiveautomation.com/u/brandon1)\
**Post date:** [December 2, 2020, 9:49pm UTC](https://forum.inductiveautomation.com/t/database-clustering-with-ignition/41146/4 "2020-12-02T21:49:14Z")

</div>

@mazeyrat How reliable has that cluster been. I have been using classic replication up until now and it breaks every now and again. Was it much more difficult than classic master-master replication to setup?

---

<div class="post-metadata">

**Author:** ![Jmoller](https://avatars.discourse-cdn.com/v4/letter/j/0ea827/32.png) [@Jmoller](https://forum.inductiveautomation.com/u/Jmoller)\
**Post date:** [December 3, 2020, 5:34pm UTC](https://forum.inductiveautomation.com/t/database-clustering-with-ignition/41146/5 "2020-12-03T17:34:25Z")

</div>

We were having a lot of problems with our replication breaking too. You should take a look at replication with [GTIDs](https://dev.mysql.com/doc/refman/8.0/en/replication-gtids.html). Was a huge improvement for us.