I've looked at implementing a mysql-cluster in great detail and let it go because it's mostly meant for a setup with a fixed database-size. If you experience (large) growth in your database volume clustering is not very suitable (we're in that situation)
I'd agree, database clustering has to be planned although replication is fairly straight forward to allow a significant increase in read access. You may want to consider partitioning databases though to allow multi-master scalability. i.e. one partition for search another for user data another for content or media etc. I did a nice graphic here for simple MySQL database replication. http://ainkaboot.co.uk/dev/cluster-architecture.php#database-replication Regarding file system selection fro clustering you need to implement a couple of production test beds to get a real feel for which will perform best. I think we've covered the main ones though. Hanni -- E-mail: [EMAIL PROTECTED] Mobile: 07985580147 Website: <a href="http://ainkaboot.co.uk";>http://ainkaboot.co.uk</a> -- [email protected] mailing list
