MySQL Cluster IaaS best practices f

MySQL Cluster IaaS best practices for Azure – High Availability, Fault Tolerance, Scalability
MySQL集群的最佳实践–Azure的IaaS的高可用性、容错性、可扩展性

Introduction
MySQL Cluster, if used correctly, has proven to be one of the most fault tolerant, scalable and real-time distributed Active/Active-capable enterprise data storage solutions. Web providers with tons of daily visits like Paypal and Zillow, as well as leading telecommunications and network equipment providers, including Alcatel-Lucent, AT&T, BT, and Ericsson have successfully deployed MySQL Clusters. You can listen to Paypal Chief Architect talk about using MySQL cluster for Paypal fraud detection in this video . They use the MySQL Cluster Carrier Grade Edition (“CGE”) which includes support and useful enterprise tools – but the MySQL Cluster Community edition is free to try out and play around with.


So why another best practices guideline for MySQL Cluster? Because when it comes to deploying and getting the best out of MySQL on Azure as an IaaS solution, we have to keep certain things in mind that is not necessarily covered very well out there today. Oracle has a whitepaper that is intended to be on the topic of MySQL for cloud – it is called “A Guide to MySQL for SaaS”. However, I found that it is more of a marketing material than being a technical guide. Also, it covers all MySQL offerings broadly, and none very deeply, including MySQL Cluster.



Which brings me to the distinction， MySQL Cluster is not the same asMySQL Database (which, in short, is just “MySQL”). They do not follow the same release cycle and version number patterns. As of this blog post, the GA version of MySQL Cluster is 7.4, but the GA version of (simply) MySQL is 5.7. MySQL Cluster does not use the same engine as MySQL – it uses a different engine called “NDB Cluster”. MySQL Cluster does not store the data co-located with the mysqld daemon, it uses separate data nodes. It is a very different beast in that sense. Of course, it is still the same in one sense, but the difference is important to note for this blog post, because we are going to explore MySQL Cluster on Azure. On the contrary, this article and this blog post of mine deals with certain best practices of using MySQL on Azure.
PaaS versus IaaS MySQL Cluster for Azure



ClearDB now provides PAAS MySQL Clusters on Azure as well. In fact, their offering seems very robust and technically a lot more attractive than managing your own instances of MySQL Clusters because of therecently announced option of Premium Dedicated Clusters.
I say that because personally, PaaS is always more attractive than IaaS, because you do not have to worry about maintaining/ monitoring/ upgrading your infrastructure, you do not have to worry about the up-time SLA or handle scaling your VM-s yourself. However, I am not sure of how ClearDB stacks up against Azure IaaS cost-wise. Though I have not done an accurate cost comparison analysis between these choices, it is clear to me that MySQL Cluster demands Azure VM-s of bigger sizes because of its memory needs. Therefore, none of the options promise to be cheap, but I am sure both of them are cheaper than having on-premises servers which tend to be severely under-utilized and almost always end up having a higher TCO because of man-hours spent in maintaining these servers, money spent behind refreshing hardware, etc.



This blog post is about IaaS – where you set up the MySQL Cluster yourself on Azure. I wrote another blog post about the actual process of creating a MySQL Cluster on Azure. I will not cover the same here again. This one will be about architectural best practices regarding high availability, fault tolerance and geo-replication.
What about Performance? 


Today, we will cover High Availability, Fault Tolerance, Scalability and some thoughts on Geo Replication related to MySQL Cluster on Azure. We will leave the performance for another day. Why? A few thoughts:
There are a lot of articles on the internet that focuses on performance optimization, fine tuning and cluster configuration for optimum MySQL cluster performance. Most of these techniques are specific to MySQL Cluster and will work regardless of where it is running – on-premises or cloud, AWS or Azure. However, in my opinion, HA and Fault Tolerance aspects are different on the cloud, and need special considerations.
 

You will hear a lot of great things about MySQL Cluster performance. Sometimes it gets difficult to sieve through results published by people trying to sell something versus people stating facts in a blunt way. Not every product is suitable for every use case. You get a feature at the cost of another, trade-offs are made – but these trade-offs are sometimes not discussed openly. What is the trade-off involved with MySQL Cluster? This is a quote from an official MySQL Cluster white paper: “MySQL Cluster is a distributed, shared-nothing data store that provides very high, scalable performance for applications that largely use pri

結果 (中文) 1:

MySQL 集群 IaaS azure — — 高可用性、 容错能力、 可扩展性的最佳做法MySQL集群的最佳实践 — — Azure的IaaS的高可用性、容错性、可扩展性介绍MySQL 群集中，如果使用正确，已被证明是一个宽容的、 可扩展的、 实时的大多数故障分布式主动/主动有能力的企业数据存储解决方案。吨的日常访问 web 提供商喜欢贝宝和 Zillow，以及领先电信和网络设备提供商，包括阿尔卡特-朗讯、 美国电话电报公司、 BT 和爱立信已经成功地部署 MySQL 集群。你可以听听 Paypal 首席架构师谈贝宝欺诈检测在这个视频中使用 MySQL 群集。他们使用 MySQL 集群载体年级版 （"专家咨询小组"），包括支持和有用的企业工具 — — 但 MySQL 群集社区版是免费试用和玩弄。那么为什么另一个 MySQL 群集的最佳做法指南吗？因为部署和获致最佳的 MySQL 在 Azure 作为 IaaS 解决方案上的时候，我们不想让某些东西记住，不一定今天被盖，好在那里。Oracle 拟云 MySQL 的主题的白皮书 — — 它被称为"指南到 MySQL 的 SaaS"。然而，我发现它是更多比一本技术指南的营销材料。而且，它涵盖所有 MySQL 产品广泛地说，并没有很深，包括 MySQL 群集。这使我想到的区别，MySQL 集群不是相同的 asMySQL 数据库 （即，简单地说，只是"MySQL"）。他们并不跟相同的发布周期和版本的数字模式。如这篇博客，GA 版本的 MySQL 集群是 7.4，但是 （只是） MySQL 的 GA 版本是 5.7。MySQL 集群不作为 MySQL 使用相同的发动机 — — 它使用不同的引擎，被称为"NDB 群集"。MySQL 集群不存储数据共存与 mysqld 守护进程，它使用单独的数据节点。它是一个非常不同的野兽，在这个意义上说。当然，它仍然是相同的在某种意义上说，但区别是重要注意事项这篇博客，因为我们将要探讨 MySQL 群集在 Azure 上。与此相反，这篇文章，这篇博客我处理的 azure 平台上使用的 MySQL 的某些最佳做法。PaaS 与 Azure 的 IaaS MySQL 群集ClearDB 现在提供 PAAS MySQL 集群在 Azure 上一样好。事实上，他们的产品似乎非常稳健和技术上更具吸引力比管理你自己的 MySQL 集群实例 therecently 宣布溢价专用集群选项。我说，因为就个人而言，PaaS 始终是更有吸引力比 IaaS，因为你不需要担心维护 / 监测 / 升级您的基础架构，你不需要担心正常运行时间 SLA 或缩放您的 VM s 的句柄。然而，我不确定如何 ClearDB 栈和 Azure IaaS 优胜。尽管我不做这些选择准确的成本对比分析，很明显我 MySQL 群集要求蔚蓝 VM-s 由于其内存更大尺寸的需要。因此，选择都不答应会便宜，但我敢肯定他们俩都是便宜比有上-处所趋于严重利用的服务器和几乎总是最终因为工时花费在维护这些服务器有更高的 TCO 钱花背后刷新硬件，等等。这篇博客是关于 IaaS — — 在那里你设置 MySQL 群集自己在 Azure。我写了另一篇博客关于 azure 平台上创建一个 MySQL Cluster 的实际过程。我将不包括这也一样。这将是关于建筑高可用性、 容错能力和土力工程处复制方面的最佳做法。性能怎么样呢？今天，我们将介绍高可用性、 容错能力、 可扩展性和土力工程处复制一些思考相关到 MySQL 群集在 Azure 上。我们将离开，另一天性能。为什么呢？几个想法 ︰有很多文章在互联网上，重点是性能优化、 微调和优化 MySQL 群集性能的群集配置。大部分的这些技术是特定于 MySQL 群集，将工作无论在哪里它正在运行 — — 对处所或云，AWS 或 Azure。但是，在我看来，房委会和容错方面不同于云层之上，并需要特殊考虑。 关于 MySQL 群集性能，会听到很多伟大的事情。有时它获取难筛通过结果发表人试图出售某个东西而不生硬地陈述事实的人。不是每个产品是适合每个用例。你得到而牺牲其他的功能，权衡了 — — 但这些权衡取舍有时不公开讨论。什么是交易涉及与 MySQL 集群？这句话出自官方的 MySQL 集群白皮书:"MySQL 群集是分布式的、 无共享的数据存储区，提供非常高、 可扩展应用程序的性能，很大程度上使用 pri