mariadb - Synchronous vs Asynchronous Clustering -
mariadb - Synchronous vs Asynchronous Clustering -
i reading mariadd knowledge base of operations on galera cluster , came across this:
the basic difference between synchronous , asynchronous replication "synchronous" guarantees if changes happened on 1 node of cluster, happened on other nodes "synchronously", or @ same time. "asynchronous" gives no guarantees delay between applying changes on "master" node , propagation of changes "slave" nodes. delay can short or long. implies if master node crashes, of latest changes may lost
with lastly sentence, have understood though updates on slave in asynchronous cluster setup not performed @ same time, logs these updates bin log file updates beingness made on master. in case master crashes before info passed on slave, updates still go ahead when master restored since bin log file logged updates. can please tell me if understanding wrong , clarify on matter me please. thanks.
in illustration of normal replication pair, slave grab after master comes back. assuming master come back, wouldn't lose info if master permanently dead, info lost. knowledge base of operations article mention talking replication delay , not overall integrity of replication stream.
with normal replication, if slave io thread (the part gets replication events master) able maintain master, slave may lose couple seconds if master crashes. however, if cannot maintain , illustration 1 hr behind, slave lose access 1 hr of data. way lose access info on slave if have max relay log size set , reached.
galera makes sure write sent every node in cluster before committed on of nodes 1 time node write done on commits write, of other nodes commit same write. galera, writes happen @ same time on every node. losing node @ time during normal operation not cause info loss.
mariadb mysql-cluster galera
Comments
Post a Comment