Wed 16 May 2007
New alpha release 1.0-pre4 of the MySQL Master-Master Replication Manager. This release has lots of major fixes and I’m glad to announce first sponsored port of mmm to non-linux platform - it has been ported to Solaris 10. So, here are our changes in this version:
- Real checks timeouts - I’ve found and fixed lots of problems in checks timeout code and now if you specified in your mmm_mon.conf, that some check should timeout in 5 sec, it would timeout correctly on all supported platforms.
- External third-party tools using - On all supported non-linux platforms mmm will use system binaries for fping and arp_ping so porting to another platforms would be much easier.
- Agent notifications fix - Now we don’t try to notify dead agents about cluster changes and additionally we have 10 sec timeout on notification sends to prevent monitoring from lagging on network connection timeouts.
- Bundled fping and send_arp - We have both used third-party tools used in mmm bundled in our distribution as separate build trees (you could find and build/install them from contrib directory).
- Flexible perl binary location - We’re using “#!/usr/bin/env perl” as shebang line in our perl scripts so you can use any perl interpreter just by placing it earlier in your PATH variable.
Notice: If you’ll try to install this version, try to run bin/sys/fping and bin/sys/send_arp on your server before installation. If you’ll notice any errors, feel free to build binaries for your platform using contrib/* sources (you’ll need gcc and libnet installed).
So, as you can see, mmm development goes forward and we’re fixing some problems trying to make this software mature. If you want to help us, you can send your comments to mmm-devel mailing list, post your bug reports to our bug tracking or sponsor any changes you need
- Data Recovery Toolkit for InnoDB Released
- Oracle SQL Developer (formerly Project Raptor) Release 6 is Out
- MySQL Master-Master Replication Manager 1.0 Released
- Best Tech Videos 2.0 has been released!
- MMM Release 1.0-pre3
2007-06-05 at 4.19 pm
this is a repost cuz not sure my email went through…
This looks like a great piece of software, I am considering setting it up.
I have a question.
If I setup a Master-Master system, without a mysql ndb manager,
basically 2 boxes that replicate eachother, using MMM to manage it…
If MMM recognizes box 1 as writer, and box 1 and 2 as readers…
lets say that box 1 goes down for 2 hours.
during this time, MMM will forward all writer and reader queries to box 2.
then box 1 comes back online. NOW, box 1 has 2 hours worth of binary logs to
process in order to get back up to date with box 2.
What will happen?
A. MMM will switch back writer roll to box 1 immediately, but if a query comes in
during the time that box 1 is processing its catch-up logs, there will be a conflict
B. MMM will keep the writer roll on box 2 until box 2 files
C. MMM will keep the writer roll on box 2 until box 1 has fully re-synched with box 2.
thanks!