StrongKey has identified a corner-case where its replication logic can produce an anomaly where some types of transactions sent by Publisher nodes are processed in reverse order on Subscriber nodes – thereby creating an inconsistency in the state of the MariaDB database in the cluster.

StrongKey is working on creating a permanent solution to this problem, but it is likely to take a few months to design, develop, test and release the long-term solution. This document is intended to use MariaDB’s Audit logging feature in the Tellaro Appliance to identify when that anomaly takes place so manual corrective action can be applied to synchronize the cluster’s database contents.

The following steps are required to enable Audit logging within MariaDB. Please be aware that turning on this feature generates additional log files that must be monitored to ensure it does not consume more space than necessary.