Re: Pointers to Mysql Replication
On 7/6/2015 1:39 PM, Claudio Nanni wrote: Hi Jatin, Say if i am using a DB instance for quiet some time on node-1 and it has data in it. If i decide to have replication with another DB instance , will all the data from node-1 be first replicated to node-2's DB ? Or will it just start the DB replication from the point where i configured DB replication ? Whatever method you use (traditional asynchronous Replication or Galera) when you add a new node (either a Replication Slave or a Galera Node) it has to acquire the full (current) dataset and then start replication from that point. With Replication you need to do it manually by making a backup of the Master, with Galera it is automatic, the newly added node will request to be synced with the cluster and it will receive the backup from one of the nodes of the cluster. Cheers -- Claudio Thanks for the responses Claudio. I will go with Master-Master replication and test it out. Thanks Jatin
Pointers to Mysql Replication
Hi All We are basically intending to implement High Availability for our application. In this regard , we want to use Mysql replication for this purpose. We would have a two-node cluster , say node-1 node-2. Assume that if node-1is functioning we want the DB changes on it to be replicated onto the DB of node-2. If node-1 goes down due to say power failure then node-2 will become active and it will start servicing application requests. And if node-1 is recovered again then any DB chages that were done on node-2 should be replicated again on node-1 so that in case of power failure in node-2 , node-1 can start the application and DB and start servicing application requests. Appreciate if you can provide some pointers of reading in this regard and the type of solution that i should implement to achieve it. Thanks Jatin
Re: Pointers to Mysql Replication
On 7/5/2015 10:48 PM, Claudio Nanni wrote: Hello Jatin, We are basically intending to implement High Availability for our application. In this regard , we want to use Mysql replication for this purpose. Your scenario(MySQL Master/Slave with Failover/Failback procedures) has been a typical one for ages now, so I am sure many good advices about it will arrive. While, I just want to bring into the table the possibility to use Galera replication which is synchronous*, multi master, and does not need failover/failback procedures, nodes syncs and desyncs automatically. Indeed I believe that this simple Master/Slave traditional scenario can represent an interesting (base case) application for Galera, I'd like other expert opinions on this too. Galera is of course a bit more complex so this has also to be taken into account. *(It has an optimistic multinode transactional approach so that in some cases a transaction might be rolled back in case of conflicts.) Cheers -- Claudio Thanks Claudio, I think having a master-master replication is what i precisely need. Basically if my application writes on the DB on node-1 it should be replicated to the DB running on node-2. After a failover my application runs on node-2 and when it writes to the DB on node-2 it should be replicated to the DB on node-1. I have a question here though, Say if i am using a DB instance for quiet some time on node-1 and it has data in it. If i decide to have replication with another DB instance , will all the data from node-1 be first replicated to node-2's DB ? Or will it just start the DB replication from the point where i configured DB replication ? Thanks Jatin
