Migration from Innodb to NDB obstacles and problems?

I have a highly normalized and indexed innodb database (the search is managed by an external sphinx server), which I am considering to move to NDB to handle possible fast mega flow into traffic.

At best, from my research and understanding, this is not a very difficult maneuver, since I do not have full text fields (at best, varchar (256)), and the search is handled from the outside anyway.

I really understand that my connection requests will be greatly degraded, however, I mean this by caching most requests with memcached (also external).

Is there anything else I should know about when considering this migration? The get-up-and-go document presented at http://www.mysql.com/products/cluster/get-started.html#quickstart makes installing for Linux fairly easy, although I'm not a 100% better way to do backups. copies and add new nodes (assuming I just take EBS snapshots through AWS, the system is currently running on EC2).

Any wisdom from the ndb gods?

+4
source share
1 answer

it is worth checking the functional differences between MySQL Cluster (NDB) and InnoDB, see the docs here: http://dev.mysql.com/doc/refman/5.5/en/mysql-cluster-compared.html

In addition, the Deployment Best Practices Webinar has a section on moving from innodb to the cluster (note: registration is required): http://mysql.com/news-and-events/on-demand-webinars/display-od -559.html

Any questions, please send to the forums forum of the cluster forums.mysql.com/list.php?25

+2
source

Source: https://habr.com/ru/post/1384795/


All Articles