探索MySQL 8.0.11及以上高可用性：InnoDB Cluster详解

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

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

领优惠券(最高得80元）

资源详情

资源推荐

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页未读，继续阅读

tlforest

粉丝: 27
资源: 198

会员权益专享

探索MySQL 8.0.11及以上高可用性：InnoDB Cluster详解

Introducing InnoDB Cluster--2018

MySQL High Availability 2nd 原版pdf by Bell

MySQL High Availability

近五年的MySQL书记

introducing erlang: getting started in functional programming

create lifecycle

The dependencies of some of the beans in the application context form a cycle: studentController ┌─────┐ | studentServiceImpl

Watermarking Deep Neural Networks

Write a high converting sales focused ecommerce product description for[insert product name] With the following features

balanced crossentropy

帮我写一篇介绍公司AI产品的广告

Adaptive Normalized Risk-Averting Training for Deep Neural Networks

time.sleep(args.rank * 0.02)

introducing python by bill lubanovic

基于卷积神经网络的图像识别外文翻译

有没有sqlserver2022的书籍

会员权益专享

最新资源