Re: MySQL [was: Re: Dr. Miguel 'Optimistic Locking' Arroz [was Re: WebObjects stress Testing tool?]]
Re: MySQL [was: Re: Dr. Miguel 'Optimistic Locking' Arroz [was Re: WebObjects stress Testing tool?]]
- Subject: Re: MySQL [was: Re: Dr. Miguel 'Optimistic Locking' Arroz [was Re: WebObjects stress Testing tool?]]
- From: Kieran Kelleher <email@hidden>
- Date: Fri, 4 Dec 2009 21:23:38 -0500
On Dec 4, 2009, at 8:11 PM, Guido Neitzer wrote:
On 4. Dec. 2009, at 11:16 , Kieran Kelleher wrote:
So, to sum up the pros and cons we heard in the discussion:
FOR MySQL
- Free
- Easy to setup and configure
- Clustering engine
I have read a bit about this part as I'm always curious about
synchronous multi-master clustering support in DBs. From Are people
here referring to NDB Cluster? From reading the white papers I was
kind of wondering how this could in any way be used in the typical
(outside big corporations) requirements. Is somebody here actually
using this?
And I'm not talking about asynchronous replication, I'm talking
about real multi-master cluster with guaranteed integrity.
- Easy reliable replication
Hmmm. Way back when we used it, it wasn't reliable. Every now and
then slaves had to be completely rebuild. And it also wasn't
straightforward as soon as something wasn't as expected.
In 4.1 there was the occasional hiccup where you had to either (1)
rebuild, or (2) check the actual statement which usually was an insert
duplicate, and if that statement had already been executed, then just
do a single statement skip and off it went again. However, I have not
had a single slave hiccup since all the slaves were upgraded to 5.0.xx.
In any case, if you had a at least 2 slaves, then the easy solution
*without* doing a full dump of the master and reconfiguring was to
stop a good working slave, literally copy the data directory and
replace the one on the bad machine and start both up again. However,
not a problem for me since 5.0.xx. There was one setting needed to
ensure you could do this though (IIRC the slave name - used for
replication log names - had to be the same or sth like that, but this
again was just a property setting in my.cnf)
Guido, I do appreciate your input here, especially since you have the
advantage of a unique perspective
AGAINST MySQL
- Lack of deferred constraints
- Lack of transactional DDL (roll back failing migrations for
example). As Mike pointed out, neither does Oracle, so not alone
there.
All toys ... :-P
Take care,
Guido
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden