探索2018年MySQL高可用性新进阶：InnoDB Cluster实践指南

需积分: 9 34 浏览量更新于2023-05-22 收藏 6.82MB PDF 举报

身份认证购VIP最低享 7 折!

领优惠券(最高得80元）

《2018年引入InnoDB Cluster：学习MySQL高可用性架构》是一本由Charles Bell编写的书籍，旨在帮助读者深入了解和掌握MySQL中的最新高可用性功能。InnoDB Cluster是MySQL数据库的一种关键特性，它提供了数据库的集群解决方案，旨在增强系统的可用性和性能。本书的核心内容包括以下几个方面： 1. 探索MySQL的最新高可用性特性和功能：InnoDB Cluster允许数据库在多台服务器之间实现数据复制和同步，确保即使在单个节点故障时，也能维持服务连续性。作者会介绍这些新特性如何提升系统的可靠性。 2. 设置与使用InnoDB Cluster作为HA解决方案：读者将学习如何在现有的MySQL环境中部署和配置InnoDB Cluster，包括配置节点、网络拓扑以及数据复制策略。 3. 迁移至MySQL 8的最佳实践：书中会指导读者如何将现有的MySQL服务器迁移到版本8，以利用InnoDB Cluster的优势，并处理可能遇到的技术挑战。 4. 最佳实践指南：涵盖如何有效地管理InnoDB Cluster，包括故障检测、恢复和恢复时间目标（RTO），以及如何通过负载均衡确保应用程序的稳定运行。 5. 自动故障转移的配置：书中会深入讲解如何配置服务器，确保在服务器故障时能自动切换，从而最小化对业务的影响。 6. MySQL Router的应用：读者将学习如何使用MySQL Router来管理客户端连接，实现流量的负载均衡，提高整个集群的吞吐量和响应速度。 7. 版权与法律信息：最后，版权和法律条款被详细列出，强调了所有内容的保护，并规定了复制、重印和使用方式的限制，以尊重知识产权。《Introducing InnoDB Cluster--2018》是一本实用的教程，适合那些寻求在高可用性场景下优化MySQL数据库架构的IT专业人士。通过阅读这本书，读者可以提升自己的技术能力，为企业的数据库管理提供坚实的基础。

资源详情

资源推荐

How toUse This Book

This book is designed to guide you through learning more about high availability and

MySQL InnoDB Cluster, discovering the power of X AdminAPI, and seeing how to

migrate existing and build new high-availability applications.

If you are new to MySQL and InnoDB Cluster, you should spend time going through

the first four chapters, including installing MySQL on your own system and learning how

to use MySQL Shell.

The next several chapters are designed to give you more information about the

components that make up InnoDB Cluster. I consider these required reading for anyone

who has not used MySQL Replication or Group Replication.

Once you are familiar with InnoDB Cluster and its components from reading the first

five chapters, you can work through Chapter 6 to learn the basics of setting up InnoDB

Cluster in a sandbox (on a single local machine). Chapter 7 covers MySQL Router, which

is especially important for those who want to build high-availability applications.

Chapters 8 and 9 present a complete solution that demonstrates how to build a

product InnoDB Cluster and a short, bare-bones, high-availability application in Python

and Flask that you can run on your systems to experiment with writing applications

for InnoDB Cluster. Perhaps what makes Chapter 8 especially interesting is that it

demonstrates how to run MySQL on the Raspberry Pi to form an InnoDB Cluster

running on five Raspberry Pi computers.

Planners may find Chapter 10 especially helpful in planning an upgrade to MySQL 8

and adapting InnoDB Clusters to your infrastructure.

Downloading theCode

The code for the examples shown in this book is available on the Apress web site,

www.apress.com/9781484238844. You can find a link on the book’s information page on

the Source Code/Downloads tab. This tab is in the Related Titles section of the page.

Contacting theAuthor

If have any questions or comments—or even spot a mistake you think I should know

about—you can contact me at drcharlesbell@gmail.com.

InTroduCTIon

These principles are building blocks, or steps to take, to reach higher levels of reliability

and thus high availability. Even if you do not need to achieve maximum high availability

(whereby the solution is up nearly all the time), by implementing these principles, you will

make your solution more reliable at the least, which is a good goal to achieve.

Now that you understand the goals or requirements that high availability can solve,

let’s discuss some of the options for implementing high availability in your MySQL

solutions. The following sections discuss four options for implementing goals of high

availability. By implementing all of these, you will achieve a level of high availability.

How much you achieve depends on not only how you implement these options but also

how well you meet your goals for reliability.

RELIABILITY VS.HIGH AVAILABILITY: WHAT IS THE DIFFERENCE?

Reliability is a measure of how operational a solution is over time, which covers one of the

major goals for high availability. Indeed, you could say that the ultimate level of reliability—the

solution is always operational—is the definition of high availability. To make your solution a

high-availability solution, you should focus on improving reliability.

Recovery

The easiest implementation of reliability you can achieve is the ability to recover from

failures. This could be a failure in a component, application server, database server,

or any other part of the solution. Recovery, therefore, is how to get the solution back to

operation in as little time and with as little cost as possible.

However, it may not be possible to recover from all types of failure. For example,

if one or more of your servers suffers a catastrophic disk failure, recovery may require

replacing the hardware and loss of data during the outage. For other types of failure,

recovery options may permit a faster method of returning to operation. Furthermore,

some components are more important and must be recoverable, so your efforts should

be to protect those more important components, the database being chief among them.

For instance, if your data becomes corrupt or is lost because of hardware failure, you

need to have a way to recover that data with as little loss as possible. One way to achieve

that is by keeping frequent backup copies of the data that can later be restored to recover

the data from loss.

CHAPTER 1 INTRODUCTION TOHIGH AVAILABILITY

Many tomes have been written about various strategies for backing up and restoring

your data. Rather than attempt to explain every nuance, technique, and best practice,

I refer you to the many texts available. For this book and the solutions available for

MySQL, it is sufficient to understand that there are two types of backup methods—

logical and physical—each with its own merits.

Logical Backup

A logical backup makes a copy of the data by traversing the data, making copies of

the data row by row, and typically translating the data from its binary form to SQL

statements. The advantage of a logical backup is that the data is human readable and

can even be used to make alterations or corrections to the data prior to restoring it. The

downside is that logical backups tend to be slow for larger amounts of data and can take

more space to store than the actual data (depending on data types, number of indexes,

and so on).

Physical Backup

A physical backup makes a binary copy of the data from the disk storage layer. The

backup is typically application specific; you must use the same application that made

the backup to restore it. The advantage is that the backup is much faster and smaller in

size. Plus, applications that perform physical backups have advanced features such as

incremental backups (only the data that has changed since the last backup) and other

advanced features. For small solutions, a logical backup may be more than sufficient, but

as your solution (your data) grows, you will need to use a physical backup solution.

Redundancy

One of the more challenging implementations of reliability is redundancy—having two

or more components serving the same role in the system. A goal for redundancy may be

simply having a component in place in case you need to replace the primary one. This

could be a hot standby: the component actively participates in parallel with the primary,

and your system automatically switches to the redundant component when a failure is

detected. The most common target for redundancy is the database server. MySQL excels

in this area with several features. One of the oldest redundancy features available in

MySQL is called replication.

CHAPTER 1 INTRODUCTION TOHIGH AVAILABILITY

剩余472页未读，继续阅读

白鸽-小蛋

粉丝: 10
资源: 167

会员权益专享

探索2018年MySQL高可用性新进阶：InnoDB Cluster实践指南

MySQL High Availability 2nd 原版pdf by Bell

Introducing InnoDB Cluster: Learning the MySQL High Availability Stack

linux block io: introducing multi-queue ssd access on multi-core systems

introducing python by bill lubanovic

openbmc开发笔记系列

introducing python pdf

min x1+1/3(x2+1)^2,

introducing erlang: getting started in functional programming

github入门 [introducing github]

Local-to-Global Self-Attention in Vision Transformers

cvt: introducing convolutions to vision transformers

Small but Mighty: Enhancing 3D Point Clouds Semantic Segmentation with U-Next Framework

theymleaf教程

Transformer-Based Visual Segmentation: A Survey

k-means算法的elkan

swin_transformer

balanced crossentropy

opencv svm的英文参考文献

会员权益专享

最新资源