patternsqlMinor
Is MySQL Clustering a viable option for a DB expecting 5TB of data in 5 years?
Viewed 0 times
5tbexpectingoptionmysqlforyearsclusteringdataviable
Problem
We plan to implement MySQL Clustering.The database should support 5 years of data and expected data/year is 1TB.
When we created a test enviornment with the DB size as 200GB, NDB Cluster took more than 2 hours to restart.
Is MySQL Clustering a viable option for an application that expects 5TB of data in 5 years, if yes, could you please guide on the suggested architecture and configuration for such a setup.
When we created a test enviornment with the DB size as 200GB, NDB Cluster took more than 2 hours to restart.
Is MySQL Clustering a viable option for an application that expects 5TB of data in 5 years, if yes, could you please guide on the suggested architecture and configuration for such a setup.
Solution
currently the maximum data set size is around 3TB, if you are using all in-memory data.
You can increase that if you use disk-based tables
MySQL Cluster also has very flexible replication to external storage engines, ie to InnoDB, so many users manage their "hot" data in cluster, then replicate "colder / aged" data to innodb.
There is a blog describing how to configure this here:
http://johanandersson.blogspot.co.uk/2009/05/ha-mysql-write-scaling-using-cluster-to.html
You can increase that if you use disk-based tables
MySQL Cluster also has very flexible replication to external storage engines, ie to InnoDB, so many users manage their "hot" data in cluster, then replicate "colder / aged" data to innodb.
There is a blog describing how to configure this here:
http://johanandersson.blogspot.co.uk/2009/05/ha-mysql-write-scaling-using-cluster-to.html
Context
StackExchange Database Administrators Q#23026, answer score: 3
Revisions (0)
No revisions yet.