Multi master cluster - imprudent, concurrent writes
Hey there,
We're wondering if imprudent, concurrent writes to multiple nodes in a multi-master replication mode in an active/active setup is recommended.
We're running an InnoDB cluster with 2 nodes in a multi-master replication mode with active/active setup. Each node is associated with one of our application nodes. Each application node is only using the mysql node it's been associated with and those application nodes imprudently and concurrently write (and read) to the database. This means reads and writes to the same schemas can happen simultaneously on different MySql nodes. We are using also FK cascades in the schemas.
We are wondering if this is a recommended and supported way of using multi-master replication with an active/active setup. With other words, can we continue to imprudently and concurrently write to different MySql nodes of the same cluster or would it be better to adjust the application logic so that only one MySql node is being written to at a time?
Could we run into any kind of performance problems if we continue using the cluster as described above?
Any comments and/or suggestions are more than welcome!
Thanks!
Edited 1 time(s). Last edit at 05/31/2021 09:54AM by Jack Hanson.
Subject
Views
Written By
Posted
Multi master cluster - imprudent, concurrent writes
1049
May 31, 2021 09:18AM
Sorry, you can't reply to this topic. It has been closed.
Content reproduced on this site is the property of the respective copyright holders.
It is not reviewed in advance by Oracle and does not necessarily represent the opinion
of Oracle or any other party.