145 reputation
110
bio website
location
age
visits member for 1 year, 8 months
seen Jul 20 '13 at 5:25

Aug
11
awarded  Popular Question
Dec
7
awarded  Popular Question
Jul
16
awarded  Tumbleweed
Jun
26
awarded  Notable Question
Apr
5
awarded  Popular Question
Dec
29
comment MySQL Replication and High Availability
I looked into DRBD today, and correct me if I'm wrong, bit it seems it is a very complex approach, and recovering data after failover with DRBD is scary... I was wondering aren't any simpler way of doing this? Like configuring pacemaker and corosync to take care of fail-over, and have mysql to take of replication? (I'm just trying to show a demo to some customers and see what is their reaction, in case I get positive feed back I can assign more resource on it, and do the best approach. I'm just looking for some easy-to-setup approach, rather busy with other stuff than lazy to set DRDB up)
Dec
29
comment MySQL Replication and High Availability
I wish I could have up voted your answer twice :) thank you again once again.
Dec
29
comment MySQL Replication and High Availability
Do I need to use any other 3rd party application to do the fail-over for me (switch to other server in case of failure) or does XtraDB would do it for me?
Dec
29
comment MySQL Replication and High Availability
Thank you for your complete answer, I'm using InnoDB, so I guess I would go for DRBD... they have lots of documentation on their website as well. But about the Replication lag in Master-Master mode which you've mentioned... would it be very obvious if you have both your nodes in the same geographic place, and have them connected through cable?
Dec
29
awarded  Supporter
Dec
29
accepted MySQL Replication and High Availability
Dec
29
accepted Mysql replication - Error No. 1146&1062
Dec
25
awarded  Teacher
Dec
25
comment Mysql replication - Error No. 1146&1062
what if I store data with diff ID (even on one server, and odd on the other one)? plus I'm not going to use it like that, I'm gonna use some sort of load balancing strategy: either write with one and read with the other, or have one of them like hot standby, or... any how, as I wrote in my question, I'm just playing around to learn...
Dec
25
asked MySQL Replication and High Availability
Dec
25
awarded  Commentator
Dec
25
comment Mysql replication - Error No. 1146&1062
This is wrong man! I have SRV_A and SRV_B, and I have only one DB on both with only one table in it! No difference which server I commit my changes to, it would be replicate on the other server as well.
Dec
25
comment Mysql replication - Error No. 1146&1062
I think what you don't get is, naturally while one node is committing changes, obviously it's master and the other node is its slave. But the other one can be master if you just connect to it! What I'm trying to say is, master-master replication is a two-way master-slave replication. Each node is master and slave to the other node, no fixed "role".
Dec
25
comment Mysql replication - Error No. 1146&1062
mfouilleul, I'm trying to learn here dude, and there are many stuff I don't know about... but correct me if I'm wrong! Isn't a database a collection of data sets? so same databses is different with same data sets? Beside, what I setup yesterday (I call it master-master replication cause thats what it calls, you can call it wtv though) which gives me the ability to write on ONE table of ONE database from TWO different nodes(masters) and changes are done to the SAME database on both NODES!
Dec
25
answered Mysql replication - Error No. 1146&1062