"MySQL" undo,redo,2pc, Recovery mind Map

A preface
Originally intends to continue to study InnoDB lock mechanism and complete the second article, when looking for information, I miss the previous csdn's public class "in-depth understanding of MySQL UNDO,REDO,MVCC." Then went to another road, the MySQL IO level of knowledge review, deepened the MySQL data consistency, master-slave consistency of understanding. This article is a combination of video and related data to organize a mind map, summary of the time, part of the Os/mysql crash example is not completely given, the future also needs to be perfected, want to learn more about this knowledge of the students, can be their own for a variety of write failure scenarios, and the Lord never consistent scene analysis, I believe that having experienced such a comprehensive analysis, it is very helpful for us to solve the problem of consistency of production environment data.

Two Mind map (will be updated gradually)

MVCC is another big pit, waiting to be filled.

Three reference articles
[1] MySQL database InnoDB storage Engine log roaming (1)
[2] MySQL database InnoDB storage engine log roaming (2)
[3] MySQL database InnoDB storage engine log roaming (3)
[4] Talking about MySQL's two-phase commit protocol
[5] Mysql-groupcommit
[6] MySQL data loss scenario analysis

Original blog:

http://blog.itpub.net/22664653/viewspace-2131353/

"MySQL" undo,redo,2pc, Recovery mind Map