MySQL Clustering Software Launched 48
lawrencekhoo writes "MySQL AB announced yesterday that software for building a
MySQL Cluster
will be available for download by the end of April. Articles available from
Computerworld,
Internetnews,
Linux Electrons,
and PHP Architect.
Great! Now my website can finally have 99.99% availability ..."
More info... (Score:5, Informative)
Here are some direct links to more information:
Oh, and they say availability is 99.999%, not just 99.99%
Re:More info... (Score:2)
Yes, but they're rounding it down a bit. =^^=
Re:More info... (Score:2)
Re:More info... (Score:2)
all that info is just PR info.
Does anyone know where I can get some
documentation, or better yet a HOWTO.
set nitpicking = on (Score:2, Interesting)
It's nice to start out a press release with a lie, isn't it? As far as I know, the title of the world's most popular open source database (meaning it has the most installs around the world) belongs to the Berkley DB [sleepycat.com].
Re:set nitpicking = on (Score:2)
Re:set nitpicking = on (Score:1)
Re:set nitpicking = on (Score:1)
However, if you believe that by not mentioning this it is open to any interpretation possible i would suggest that neither BerkleyDB nor MySQL are the most popular. I am sure ext2fs is installed on more machines than MySQL so the article is lying. It's not MySQL , but ext2fs that is the most popular database.
He
Re:set nitpicking = on (Score:1)
Re:set nitpicking = on (Score:5, Insightful)
Re:set nitpicking = on (Score:2, Interesting)
Re:set nitpicking = on (Score:1)
set error_detection = on (Score:5, Informative)
Berkely DB is code that manages a data store, and you access the data using method calls within your app (you compile their code with your project), NOT using SQL, and NOT connecting to an independant application. Remote access n/a, no ODBC or JDBC, etc. etc.. Great product, but a completely different animal from MySql and other relational databases.
In fact, MySql used to offer Berkeley DB (as opposed to InnoDB, etc.) as a data storage option WITHIN the MySql product.
Re:set nitpicking = on (Score:2, Insightful)
just anything that organises data, so a filesystem would count, but that's not
how the term is generally used. Usually these days when people say database
they mean RDBMS.
The other thing is, most installs is not the only reasonable measure of
popularity. I'm pretty sure more people have daily interaction with MySQL
than with Berkeley DB directly. Berkeley DB is installed so widely because
it's been around longer and because certai
Re:set nitpicking = on (Score:1)
Re:set nitpicking = on (Score:1)
What about PG? (Score:5, Interesting)
From what I've read it looked very, very prommising, but it doesn't do much good if it's on paper only...
In memory only? (Score:4, Insightful)
Re:In memory only? (Score:1)
Re:In memory only? (Score:5, Informative)
From the way I'm reading it, this type of cluster would be most ecomomically used for in conjunction with a traditional replicated mysql database. You would use clustered engine for transactional tables where a large number of inserts or updates occur, and for tables where you have a lot of historical or read-only data, you would use standard replication, where you could tolerate a few minutes without the ability to insert or update should the master fail. In order to reduce the memory requirements for the cluster you could also move old transactations from the transactional tables to historical tables which use InnoDB/MyISAM.
That being said, there must be SOME use of the disk on the cluster, because their recommended node system has raid + four 73GB SCSI hard drives... major overkill if everything except for OS/Software is stored in memory!
drive usage and thoughts... (Score:5, Informative)
Without ramsan style battery packed ram, there is no way any enterprise would trust clusters of any kind to ram only storage for write commits.
Looks like each write transaction will be synchronized acrossed all nodes, which would explain the gigabit and lower latency interconnects. Still, this is crazy complex to make fast and reliable.
So to make it truely synchronized, they have to write to disk, for backup/log, before committiong the data to the ram. So regardless, writes are slow and I'm waiting to see how they by-pass this disk write commit latency. Add on that they have to do this for all nodes before responding to the app, writes are crazy slow, relatively, since they can influence indices, force cache/ramed-data flushes, etc. Would be interesting to see how they handle this.
Also, I'm interested to see what type of check code/algorithm to see which NODE is healthy and which ones are corrupt (not dead since dead servers are the easiest to detect). From their diagrams, looks like N-type replication so each node is an exact synchorinized duplicate of all others. But how to know for sure which one is the "safe" one when corrupts happen?
Also, I wonder how they tackle gigantic inserts/update like "replace into table2 select * from gigantic_table1". They can't assume or dictate that we only stick to small write transactions right?
Cheap N-way synchronized replication is my and probably most dbms managers' holy grail so I'm crossing my fingers for Mysql to get this right.
Re:drive usage and thoughts... (Score:1)
Re:drive usage and thoughts... (Score:1)
However the data is written synchronously to more than a single node. So when you insert data, it is inserted into two places (or more, it is configurable) at the same time. That way even if one server goes down, you will still query from the other place.
The result of this, is that it still will scale linearly for writes as well. Keep in min
You know you're a database geek when: (Score:5, Funny)
Node requirements (Score:2, Insightful)
Is stats that you need 16GB of RAM !! Why do they say that? Doesn't the amount of RAM depends on the size of your Database? If my InnoDB database file is only 3GB why would I need more that 4GB og RAM?
Also, why the hell would you need scsi drives for an in memory database?
Re:Node requirements (Score:1)
1x Intel Xeon, Intel Itanium, AMD Opteron, Sun SPARC, IBM PowerPC
I guess they think you won't bother clustering on anything less than a hefty server. I won't be testing this at home.
Re:Node requirements (Score:3, Informative)
Does MySQL AB have credibility here? (Score:5, Insightful)
Re:Does MySQL AB have credibility here? (Score:4, Insightful)
--
lds
Re:Does MySQL AB have credibility here? (Score:2)
Alan.
.
MySQL Cluster white paper (Score:3, Informative)
For the lazy among you (and lazy you have to be to find the task of entering a few fields in a form exhiliarating), I have uploaded the MYSQL Cluster white paper to another FTP site, mirror of the file which you may access there: mysql-cluster-whitepaper.pdf [zemelon.net] (the document is a PDF file, so fear the Adobe Acrobat Reader loading time).
Re:MySQL Cluster white paper (Score:3, Informative)
MySQL Cluster technical white paper (Score:2)
Thank you for noticing this new white paper, document which I have once again mirrored and that you may find there: mysql-cluster-technical-whitepaper.pdf [zemelon.net] (181 KB in size).
Re:MySQL Cluster white paper (Score:1)
Re:MySQL Cluster white paper (Score:1)