Commit delay for MariaDB Galera cluster and MaxScale

Question

I'm working in a clustered MariaDB database with Galera and MaxScale in r/w routing.
My question is if the commit command successful return implies a completed replication or not.

This is the scenario:

I have a php application linked to MaxScale port.
This application inserts a record
Then it call using REST-API a local java application passing the new record id.
The java application is connected to the same MaxScale port, and it read the inserted record

However sometimes it looks like Java cannot find the new record just inserted.

Is it possibile that the commit is returned even if the replication is not finished and then the java cannot find the record due to replication latency?

danblack · Accepted Answer · 2025-02-13 21:15:09Z

1

Yes, there is replication latency.

A successful commit implies there isn't a conflict. The other nodes of the cluster still need to apply the commit with applier threads which is the replication delay.

ref: https://galeracluster.com/library/documentation/certification-based-replication.html

answered Feb 13 at 21:15

danblack

14.9k2 gold badges27 silver badges49 bronze badges

Sign up to request clarification or add additional context in comments.

2 Comments

Tobia Feb 13 at 21:38

Thank you for your answer, but is there any solution for my scenario? I it possible somehow to get the replication competition confirmation?

danblack Feb 18 at 21:13

Use Master_wait_gtid as part of the second select where the gtid is returned from the first insert or there is probably a maxscale way in its configuration.

Collectives™ on Stack Overflow

Commit delay for MariaDB Galera cluster and MaxScale

1 Answer 1

2 Comments

Your Answer

Hot Network Questions

Collectives™ on Stack Overflow

1 Answer 1

2 Comments

Your Answer

Sign up or log in

Post as a guest

Related