MySQL双主架构主库单点故障解决方案

在企业中，一般系统架构的瓶颈会出现在数据库这一部分，Mysql主从架构在很大程度上解决了这部分瓶颈，但是在Mysql主从同步的架构也存在很多问题。比如：

1. 关于数据写入部分(也就是主库)往往很难做到扩展，虽然很多大公司在逻辑业务方面就进行对数据的拆分，比如商品库存按照区域去拆分(一个区域走一个库存也就是一个主库,然后定时同步总的库存)，按照商品类型去划分(一个类型的商品走一套数据库)，但是这对于很多中小型公司来说实现起来还是比较困难的；

2. 主从同步一般都是一个主库，一旦主库出现问题,就有可能直接导致整个主从同步架构崩盘，虽然发现后也是可以慢慢恢复的，但是这个恢复时间对于很多公司来说是难以接受的。

今天的这篇博文主要给解决主库单点故障这个问题提供一个思路：

• 一台主库(我们称之为master-01)提供服务,只负责数据的写入；

• 拿出一台数据库服务器(我们称之为Master-02)资源做master-01主库的从库(之间做主从同步)；

• 两台主库之间做高可用,可以采用keepalived等方案(一定要保证master-01同时也要作为keepalived的主)；

• 程序在调用主库IP地址的地方写为高可用的VIP地址；

• 所有提供服务的从服务器与master-02进行主从同步；

• 建议采用高可用策略的时候,当master-01出现问题切换到master-02的时候,即使master-01恢复了,也不要让它去自动承接VIP地址,否则可能造成数据的混写

这样做可以在一定程度上保证主库的高可用，在一台主库down掉之后,可以在极短的时间内切换到另一台主库上(尽可能减少主库宕机对业务造成的影响)，减少了主从同步给线上主库带来的压力；但是也有几个不足的地方：

• master-02可能会一直处于空闲状态(其实完全可以让它承担一部分从库的角色来负责一部分查询请求的)；

• 这样真正提供服务的从库要等master-02先同步完了数据后才能去master-02上去同步数据，这样可能会造成一定程度的同步延迟时间的加长；

• 如果master-01一旦恢复正常，会不会导致数据写入混乱(这个可以在keepalived中设置响应的规则,让其不”夺权”，我们认为的去调整操作即可。

架构的简易图如下：

具体实施方案：

一、在所有需要提供服务的服务器上安装MySQL服务(建议源码安装)

1、yum安装依赖包

1. yum -y install cmake make gcc gcc-c++  ncurses-devel bison openssl-devel

2、添加MySQL所需要的用户/组

1. groupadd mysql

2. useradd -g mysql -r mysql

3、下载MySQL源码包

1. wget http://dev.mysql.com/get/Downloads/MySQL-5.5/mysql-5.5.36.tar.gz

4、创建MySQL安装所需要的目录

1. mkdir /data/mydata/{data,tmp,logs} –pv

5、解压编译安装MySQL

1. tar xf mysql-5.5.36.tar.gz

2. cd mysql-5.5.36

3. cmake . -DCMAKE_INSTALL_PREFIX=/usr/local/mysql \

4. -DMYSQL_DATADIR=/data/mydata/data \

5. -DSYSCINFDIR=/etc \

6. -DWITH_INNOBASE_STORAGE_ENGINE=1 \

7. -DWITH_ARCHIVE_STORAGE_ENGINE=1 \

8. -DWITH_BLACKHOLE_STORAGE_ENGINE=1 \

9. -DWITH_READLINE=1 \

10. -DWITH_SSL=system \

11. -DWITH_ZLIB=system \

12. -DWITH_LIBWARP=0 \

13. -DWITH_UNIX_ADDR=/tmp/mysql.sock \

14. -DDEFAULT_CHARASET=uft8 \

15. -DDEFAULT_COLLATTON=utf9_general_ci \

16. make && make install

6、为MySQL提供启动脚本

1. cp support-files/mysql.server /etc/rc.d/init.d/mysqld

7、为master-01主库提供配置文件(32G内存较为保守(满连接占用25G左右内存)的配置文件)

1. [client]

2. port = 3306

3. socket = /var/lib/mysql/mysql.sock

4. default-character-set = utf-8

5. [mysqld]

6. server-id = 1

7. port = 3306

8. user = mysql

9. basedir = /usr/local/mysql

10. datadir = /data/mydata/data

11. tmpdir = /data/mydata/tmp

12. socket = /var/lib/mysql/mysql.sock

13. skip-external-locking

14. skip-name-resolve

15. default-storage-engine = INNODB

16. character-set-server = utf8

17. wait-timeout = 100

18. connect_timeout = 20

19. interactive_timeout = 100

20. back_log = 300

21. myisam_recover

22. event_scheduler = on

23. log-bin=/data/mydata/logs/mysql-bin

24. binlog_format = row

25. max_binlog_size = 64M

26. binlog_cache_size = 1M

27. slave-net-timeout = 10

28. skip-slave-start

29. slow_query_log  = 1

30. long_query_time = 1

31. slow_query_log_file = /data/mydata/mysqllog/logs/mysql.slow

32. log-error = /data/mydata/mysqllog/logs/error.log

33. max_connections = 1000

34. max_user_connections = 1000

35. max_connect_errors = 10000

36. key_buffer_size = 32M     #以MyISAM为主的服务器,要调大此值

37. max_allowed_packet = 64M

38. table_cache = 4096

39. table_open_cache = 4096

40. table_definition_cache = 4096

41. sort_buffer_size = 512K

42. read_buffer_size = 512K

43. read_rnd_buffer_size = 512K

44. join_buffer_size = 512K

45. tmp_table_size = 64M

46. max_heap_table_size = 64M

47. query_cache_type = 0

48. query_cache_size = 0

49. bulk_insert_buffer_size = 16M

50. thread_cache_size = 64

51. thread_concurrency = 16       #CPU核数*2

52. thread_stack = 256K

53. innodb_data_home_dir = /data/mydata/data

54. innodb_log_group_home_dir = /data/mydata/mysqllog/logs

55. innodb_data_file_path = ibdata1:1G:autoextend

56. innodb_buffer_pool_size = 16G

57. innodb_buffer_pool_instances = 4

58. innodb_additional_mem_pool_size = 16M

59. innodb_log_file_size = 512M

60. innodb_log_buffer_size = 32M

61. innodb_log_files_in_group = 3

62. innodb_flush_log_at_trx_commit = 2

63. innodb_lock_wait_timeout = 10

64. innodb_sync_spin_loops = 40

65. innodb_max_dirty_pages_pct = 90

66. innodb_support_xa = 1

67. innodb_thread_concurrency = 0

68. innodb_thread_sleep_delay = 500

69. innodb_file_io_threads = 4

70. innodb_concurrency_tickets = 1000

71. log_bin_trust_function_creators = 1

72. innodb_flush_method = O_DIRECT

73. innodb_file_per_table          #是否采用单表单空间

74. innodb_write_io_threads = 8

75. innodb_read_io_threads = 8

76. innodb_io_capacity = 1000

77. innodb_file_format = Barracuda    #不开启单表单空间,此选项无效

78. innodb_purge_threads = 1

79. innodb_purge_batch_size = 32

80. innodb_old_blocks_pct = 75

81. innodb_change_buffering = all

82. transaction_isolation = READ-COMMITTED

83. [mysqldump]

84. quick

85. max_allowed_packet = 32M

86. [mysql]

87. no-auto-rehash

88. [myisamchk]

89. key_buffer_size = 64M

90. sort_buffer_size = 256M

91. read_buffer = 2M

92. write_buffer = 2M

93. [mysqlhotcopy]

94. interactive-timeout

95. [mysqld_safe]

96. open-files-limit = 10240

8、为master-02提供配置文件

1. master-02的配置文件仅需在master-01上稍作修改

2. server-id = 20

3. log_slave_updates = 1    #添加(将复制事件写入binlog,一台服务器既做主库又做从库此选项必须要开启)

4. replicate-same-server-id=0 #添加(防止MySQL循环更新)

5. relay_log_recovery = 1   #添加(MySQLrelay_log的自动修复功能)

9、为从库提供配置文件(8G)

1. [client]

2. port = 3306

3. socket = /var/lib/mysql/mysql.sock

4. default-character-set = utf8

5. [mysqld]

6. server-id = 2

7. port = 3306

8. user = mysql

9. basedir = /usr/local/mysql

10. datadir = /data/mydata/data

11. tmpdir  = /data/mydata/tmp

12. socket  = /var/lib/mysql/mysql.sock

13. skip-external-locking

14. skip-name-resolve

15. default-storage-engine = INNODB

16. character-set-server = utf8

17. wait-timeout = 100

18. connect_timeout = 20

19. interactive_timeout = 100

20. back_log = 300

21. myisam_recover

22. event_scheduler = on

23. log-bin=/data/mydata/logs/mysql-bin

24. binlog_format = row

25. max_binlog_size = 64M

26. binlog_cache_size = 1M

27. slave-net-timeout = 10

28. relay_log_recovery = 1

29. slow_query_log = 1

30. long_query_time = 1

31. slow_query_log_file = /data/mydata/mysqllog/logs/mysql.slow

32. log-error = /data/mydata/mysqllog/logs/error.log

33. max_connections = 500

34. max_user_connections = 500

35. max_connect_errors = 10000

36. key_buffer_size = 32M     #以MyISAM为主的服务器,要调大此值

37. max_allowed_packet = 64M

38. table_cache = 2048

39. table_open_cache = 2048

40. table_definition_cache = 2048

41. sort_buffer_size = 128K

42. read_buffer_size = 128K

43. read_rnd_buffer_size = 128K

44. join_buffer_size = 128K

45. tmp_table_size = 16M

46. max_heap_table_size = 16M

47. query_cache_type = 0

48. query_cache_size = 0

49. bulk_insert_buffer_size = 16M

50. thread_cache_size = 64

51. thread_concurrency = 4       #CPU核数*2

52. thread_stack = 128K

53. innodb_data_home_dir = /data/mydata/data

54. innodb_log_group_home_dir = /data/mydata/mysqllog/logs

55. innodb_data_file_path = ibdata1:1G:autoextend

56. innodb_buffer_pool_size = 2G

57. innodb_buffer_pool_instances = 4

58. innodb_additional_mem_pool_size = 4M

59. innodb_log_file_size = 512M

60. innodb_log_buffer_size = 16M

61. innodb_log_files_in_group = 3

62. innodb_flush_log_at_trx_commit = 2

63. innodb_lock_wait_timeout = 10

64. innodb_sync_spin_loops = 40

65. innodb_max_dirty_pages_pct = 90

66. innodb_support_xa = 1

67. innodb_thread_concurrency = 0

68. innodb_thread_sleep_delay = 500

69. innodb_file_io_threads = 4

70. innodb_concurrency_tickets = 1000

71. log_bin_trust_function_creators = 1

72. innodb_flush_method = O_DIRECT

73. innodb_file_per_table                #是否采用单表单空间

74. innodb_write_io_threads = 8

75. innodb_read_io_threads = 8

76. innodb_io_capacity = 1000

77. innodb_file_format = Barracuda     #不开启单表单空间,此选项无效

78. innodb_purge_threads = 1

79. innodb_purge_batch_size = 32

80. innodb_old_blocks_pct = 75

81. innodb_change_buffering = all

82. transaction_isolation = READ-COMMITTED

83. [mysqldump]

84. quick

85. max_allowed_packet = 32M

86. [mysql]

87. no-auto-rehash

88. [myisamchk]

89. key_buffer_size = 64M

90. sort_buffer_size = 256M

91. read_buffer = 2M

92. write_buffer = 2M

93. [mysqlhotcopy]

94. interactive-timeout

95. [mysqld_safe]

96. open-files-limit = 10240

10、初始化MySQL

1. /usr/local/mysql/scripts/mysql_install_db --user=mysql--datadir=/data/mydata/data/ --basedir=/usr/local/mysql

11、为启动脚本赋予可执行权限并启动MySQL

1. chmod +x /etc/rc.d/init.d/mysqld

2. /etc/init.d/mysqld start

二、 配置master-01

1、添加主从同步账户

1. mysql> grant replication slave on *.* to 'repl'@'192.168.237.%' idetified by '123456';

2. mysql> flush privileges;

2、查看主库的状态

1. mysql> show master status;

2. +------------------+----------+--------------+------------------+

3. | File             | Position | Binlog_Do_DB | Binlog_Ignore_DB |

4. +------------------+----------+--------------+------------------+

5. | mysql-bin.000009 |      652 |              |                  |

6. +------------------+----------+--------------+------------------+

7. 1 row in set (0.01 sec)

3、因为这是测试环境,可以保证没数据写入,否则需要先锁表-->查看状态-->备份数据-->查看状态(保证没变)-->解锁表

三、 配置master-02

1、配置master-02为master-01的从

1. #若是线上有数据需要先导入数据  

2. mysql> CHANGE MASTER TO  

3.  ->MASTER_HOST='192.168.237.128',  

4.  ->MASTER_PORT=3306,  

5.  ->MASTER_USER='repl',  

6.  ->MASTER_PASSWORD='123456',  

7.  ->MASTER_LOG_FILE='mysql-bin.000009',  

8.  ->MASTER_LOG_POS=652;  

9. Query OK, 0 rows affected (0.03 sec)  

10. mysql> start slave;  

11. mysql> show slave status \G  

12.   Slave_IO_Running: Yes   #确保为yes  

13.   Slave_SQL_Running: Yes  #确保为yes

2、配置master-02的同步用户

1. mysql> grant replication slave on *.* to 'repl’@’192.168.237.%' identified by '123456';

2. mysql> flush privileges;

3、查看master-02的状态

1. mysql> show master status;

2. +------------------+----------+--------------+------------------+

3. | File             | Position | Binlog_Do_DB | Binlog_Ignore_DB |

4. +------------------+----------+--------------+------------------+

5. | mysql-bin.000004 |      689 |              |                  |

6. +------------------+----------+--------------+------------------+

7. 1 row in set (0.00 sec)

四、从库根据上面步骤配置为master-02的从即可(为了节省篇幅不再一一赘述)

五、在master-01上创建一个数据库测试同步效果

六、去master-02跟从库上分别查看是否已经同步过数据来

好了，至此数据同步已经完成。关于keepalived实现双主高可用，我会总结在下篇keepalived实现MySQL高可用文章中，届时分享给各位。

原文链接：http://yanshisan.blog.51cto.com/7879234/1393063

转载于:https://blog.51cto.com/lucifer119/1394336