Mysql interview questions1/1/2023 ![]() ![]() Multi-source replication is still very new, is there any part that will change in any way? The important point here is that you consider your capacity planning and understand that have 20 servers replicating to a single, identical setup for the slave, even with multi-threading, is probably going to cause a performance issue. That is the proverbial “how long is a piece of string” question! Essentially there is no implemented limit in the server as to how many masters can replicate to a slave, that is, how many channels can be defined for replication. How many masters can I replicate to a single slave? There is currently no option for per-channel filters to be used. The replication filters are applied globally across all the channels. How do the replication filters apply now that there are multiple channels? You cannot only have a partial implementation of semi-synchronous servers in the multi-source replication setup. Similar to GTIDs, the answer here is yes, if the semi-synchronous feature is running across all servers in the replication setup. Can multi-threaded replication be used with semi-synchronous replication? These are beyond the scope of this document, but you can get further information from the knowledge base and/or online. However, it should be pointed out that there two different ways this can be implemented – database partitioning or parent commit sequencing. Yes, there is the capability to use multi-threaded slaves as the receiving server for multi-source replication. These additions are predominantly the “FOR CHANNEL” and “ALL CHANNELS” clauses to the existing commands such as:Ĭan I use multi-threaded slaves in a multi-source replication setup? The 5.7 version has introduced new syntax to manage the changes added with multi-source replication. The concept is simple, but how do I manage all the different masters connecting to the slave? The short answer is – no! It is a new feature that requires new code which is only available from 5.7 onwards. ![]() Will multi-source replication be backported to previous versions such as 5.5 or 5.1? Even with this scenario, the application should detect any exceptions and handle accordingly so the service doesn’t fail. The way the application enforces safety and avoids conflict is to make sure the masters are always working on distinct data sets. The way multi-source replication deals with this at the moment is to leave the responsibility with the application developers. With multiple masters all replicating down to a single server, there is bound to conflict at some point. How does multi-source replication deal with conflict resolution? Consolidate remote servers through a single server for geo-replication and/or data transfers.Similar to the single reporting server, but in this use case it would be a single backup server.Reduce sharded servers down to a single reporting server to give consolidated reports and viewing. ![]()
0 Comments
Leave a Reply.AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |