Upgrade to Pro
— share decks privately, control downloads, hide ads and more …
Speaker Deck
Features
Speaker Deck
PRO
Sign in
Sign up for free
Search
Search
MySQL - The Old Way
Search
Gea-Suan Lin
July 29, 2012
Technology
4
440
MySQL - The Old Way
Gea-Suan Lin
July 29, 2012
Tweet
Share
More Decks by Gea-Suan Lin
See All by Gea-Suan Lin
High Availability Vault Service on AWS Environment
gslin
0
6.8k
用 AWS CodeDeploy 解決程式佈署
gslin
0
320
MySQL to NoSQL & Search Engine
gslin
0
1.8k
用 Vagrant 與 Docker 拯救世界
gslin
1
210
Startup IT infrastructure: Developing and Working with AWS
gslin
8
3.3k
Talk about Percona XtraDB Cluster
gslin
0
170
API Design Optimized for Mobile Platform
gslin
9
8.2k
Use Facebook::Graph to write desktop application
gslin
2
440
COSCUP 2012 - MySQL System Stability
gslin
17
11k
Other Decks in Technology
See All in Technology
技術広報経験0のEMがエンジニアブランディングをはじめてみた
coconala_engineer
1
140
社内共通ルールを値オブジェクトにして社内ライブラリとして運用してみた話
leveragestech
2
1.2k
生成AIの不確実性と向き合うためのオブジェクト指向設計
tkikuchi1002
2
700
LLMプロダクト事業の立ち上げにおける挑戦
layerx
PRO
7
1.5k
GraphQLに入門してみた
chiroruxx
2
130
検証からプロダクトへ: シームレスなLLM開発の ためのしくみ作り
nunukim
1
210
10分でわかるfreeeのQA
freee
0
260
コードレビューを支援するAI技術の応用
akkie76
3
200
Getting started with controlling LEGO using Swift
hcrane
0
140
オブジェクトのおしゃべり大失敗 メッセージングアンチパターン集 / messaging anti-pattern collection
ytake
0
340
長文から長文を生成するLLMツールをオープンソースで作ってみた。
tomohisa
2
150
KubeCon EU: Unlocking new Platform Experiences with Open Interfaces
salaboy
1
380
Featured
See All Featured
Debugging Ruby Performance
tmm1
68
11k
The Straight Up "How To Draw Better" Workshop
denniskardys
227
130k
Mobile First: as difficult as doing things right
swwweet
215
8.5k
CSS Pre-Processors: Stylus, Less & Sass
bermonpainter
352
28k
GraphQLの誤解/rethinking-graphql
sonatard
48
9.1k
The World Runs on Bad Software
bkeepers
PRO
60
6.6k
Build The Right Thing And Hit Your Dates
maggiecrowley
23
1.9k
StorybookのUI Testing Handbookを読んだ
zakiyama
10
4.5k
What's new in Ruby 2.0
geeforr
335
31k
Imperfection Machines: The Place of Print at Facebook
scottboms
257
12k
Ruby is Unlike a Banana
tanoku
95
10k
Six Lessons from altMBA
skipperchong
19
2.9k
Transcript
MySQL - The Old Way Gea-Suan Lin
Old != Bad
In this case, Old implies Reliable
Reliable
We are familiar with these issues,
We can workaround these issues
So...
First Solution
Built-in Replication
http://dev.mysql.com/ doc/refman/5.5/en/ replication.html
The Good Part
Simple
Dead Simple Setup
Dead Simple Concept
Master logs changes
Slave applies changes
The Bad Part
Async
Means...
Replication Lag
When you write data to master,
It’s possible unable to read from slave
Workaround
Always use master if you write data
The Worst Part
Application cannot write after master crash
This derives...
Second Solution
Master-Master
Two MySQL servers
Set each other as master server
The Good Part
Both MySQL servers can be written
The Bad Part
Data inconsistent
MySQL Server A TRUNCATE TABLE t; INSERT t SET i=1;
MySQL Server B TRUNCATE TABLE t; INSERT t SET i=2;
MySQL Server A TRUNCATE TABLE t; INSERT t SET i=1;
TRUNCATE TABLE t; INSERT t SET i=2; MySQL Server B TRUNCATE TABLE t; INSERT t SET i=2; TRUNCATE TABLE t; INSERT t SET i=1;
Result
MySQL Server A i=2 MySQL Server B i=1
Workaround
Write one server in normal case
Write another one when primary node fails
You can write code to handle failover
But we suggest to use Heartbeat
Heartbeat can handle this failover case
When data is inconsistent,
We can use Percona’s pt-table-sync to sync data
Third Solution
DRBD + Heartbeat
DRBD is Network-based RAID-1
Block-level mirror
Heartbeat handles High Availability
http://dev.mysql.com/ doc/refman/5.5/en/ha- drbd.html
http://dev.mysql.com/ doc/refman/5.5/en/ha- heartbeat.html
The Good Part
Data consistent
You won’t need to worry about data inconsistent issue
The Bad Part
Utilization Rate
Only one server uses to serve applications
Warm up time
When I/O rate cannot catch query rate
Conclusion
DRBD has higher down-time than other twos,
And it costs higher in server hardware
But it costs lower for SA Operations
If down-time of DRBD + Heartbeat is acceptable,
You should choose it
How much down- time ?
It depends,
Usually < 30 secs to failover
With warm up time
Possible 3~5 mins for 10GB data size ?
Thanks !