The presentation I gave in the MySQL Devroom at Fosdem 2010 , summarizing the different alternatives for MySQL HA

1. MySQL HA An overview Kris Buytaert

3. „ Infrastructure Architect“

4. I don't remember when I started using MySQL :)

5. Specializing in Automated , Large Scale Deployments , Highly Available infrastructures, since 2008 also known as “the Cloud”

6. Surviving the 10 th floor test

7. DevOp

9. Not designed for high-performance

10. Not designed for high troughput (load balancing)

12. You mis out on $$$

13. Your boss complains

14. New users don't return

15. Lies, Damn Lies, and Statistics Counting nines (slide by Alan R)

17. Keep it Simple

18. Prepare for Failure

19. Complexity is the enemy of reliability

21. Realitime

23. Most of the time

25. Fans

27. Going Out Of Memory

29. If those partitions each try and take control of the cluster, then it's called a split-brain condition

32. Multiple read only nodes

33. Application needed to be modified

35. DRBD

36. MySQL Cluster NDBD

37. Multi Master Replication

38. MySQL Proxy

39. MMM

40. Flipper

43. Proxy

44. Heartbeat / Pacemaker

46. Monitor MySQL node

47. Stonith

48. $$$ 1+1 <> 2

49. Storage = SPOF

50. Split Brain :(

52. In the Linux Kernel (as of very recent)

54. Only 1 MySQL instance Active accessing data

55. Upon Failover MySQL needs to be started on other node

57. Why did the crash happen ?

58. Is my data still correct ?

60. Check your BinLog size

62. Automatic partitioning

63. Synchronous replication

64. Fast automatic fail-over of data nodes

65. In-memory indexes

66. Not suitable for all query patterns (multi-table JOINs, range scans)

71. Does not fit for all apps

73. Both nodes are slave

74. Write in 1 get updates on the other M|S M|S

78. No Application change required

79. Sends specific queries to a specific node

81. User

82. Table

83. Availability

91. OpenARK

93. Advanced Routing

94. LVS

95. Or the upcoming slides

98. master-master MySQL Servers

99. Clients machines do not connect &quot;directly&quot; to either node instead,

100. One IP for read,

101. One IP for write.

102. Flipper allows you to move these IP addresses between the nodes in a safe and controlled manner.

103. http://provenscaling.com/software/flipper/

105. Manages more than MySQL

106. ...v3 .. don't even think about the rest anymore

107. http://clusterlabs.org/

110. Think about your Data

111. Think about getting Queries to that Data

112. Complexity is the enemy of reliability

113. Keep it Simple

114. Monitor inside the DB

115. ` Kris Buytaert < [email_address] > Further Reading http://www.krisbuytaert.be/blog/ http://www.inuits.be/ http://www.virtualization.com/ http://www.oreillygmt.com/ ? !