Saltstack Official Galera Formula
Você não pode selecionar mais de 25 tópicos Os tópicos devem começar com uma letra ou um número, podem incluir traços ('-') e podem ter até 35 caracteres.

README.rst 5.4KB

9 anos atrás
9 anos atrás
9 anos atrás
9 anos atrás
9 anos atrás
9 anos atrás
123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181182183184185186187188189190191192193194195
  1. ======
  2. Galera
  3. ======
  4. Galera Cluster for MySQL is a true Multimaster Cluster based on synchronous replication. Galera Cluster is an easy-to-use, high-availability solution, which provides high system uptime, no data loss and scalability for future growth.
  5. Sample pillars
  6. ==============
  7. Galera cluster master node
  8. .. code-block:: yaml
  9. galera:
  10. master:
  11. enabled: true
  12. name: openstack
  13. bind:
  14. address: 192.168.0.1
  15. port: 3306
  16. members:
  17. - host: 192.168.0.1
  18. port: 4567
  19. - host: 192.168.0.2
  20. port: 4567
  21. admin:
  22. user: root
  23. password: pass
  24. database:
  25. name:
  26. encoding: 'utf8'
  27. users:
  28. - name: 'username'
  29. password: 'password'
  30. host: 'localhost'
  31. rights: 'all privileges'
  32. Galera cluster slave node
  33. .. code-block:: yaml
  34. galera:
  35. slave:
  36. enabled: true
  37. name: openstack
  38. bind:
  39. address: 192.168.0.2
  40. port: 3306
  41. members:
  42. - host: 192.168.0.1
  43. port: 4567
  44. - host: 192.168.0.2
  45. port: 4567
  46. admin:
  47. user: root
  48. password: pass
  49. InnoDB parameters
  50. =================
  51. - **innodb_buffer_pool_size** - the default value is 35% of the available ram
  52. Usage:
  53. .. code-block:: yaml
  54. galera:
  55. master:
  56. innodb_buffer_pool_size: 1024M
  57. slave:
  58. innodb_buffer_pool_size: 1024M
  59. Usage
  60. =====
  61. MySQL Galera check sripts
  62. .. code-block:: bash
  63. mysql> SHOW STATUS LIKE 'wsrep%';
  64. mysql> SHOW STATUS LIKE 'wsrep_cluster_size' ;"
  65. Galera monitoring command, performed from extra server
  66. .. code-block:: bash
  67. garbd -a gcomm://ipaddrofone:4567 -g my_wsrep_cluster -l /tmp/1.out -d
  68. 1. salt-call state.sls mysql
  69. 2. Comment everything starting wsrep* (wsrep_provider, wsrep_cluster, wsrep_sst)
  70. 3. service mysql start
  71. 4. run on each node mysql_secure_install and filling root password.
  72. .. code-block:: bash
  73. Enter current password for root (enter for none):
  74. OK, successfully used password, moving on...
  75. Setting the root password ensures that nobody can log into the MySQL
  76. root user without the proper authorisation.
  77. Set root password? [Y/n] y
  78. New password:
  79. Re-enter new password:
  80. Password updated successfully!
  81. Reloading privilege tables..
  82. ... Success!
  83. By default, a MySQL installation has an anonymous user, allowing anyone
  84. to log into MySQL without having to have a user account created for
  85. them. This is intended only for testing, and to make the installation
  86. go a bit smoother. You should remove them before moving into a
  87. production environment.
  88. Remove anonymous users? [Y/n] y
  89. ... Success!
  90. Normally, root should only be allowed to connect from 'localhost'. This
  91. ensures that someone cannot guess at the root password from the network.
  92. Disallow root login remotely? [Y/n] n
  93. ... skipping.
  94. By default, MySQL comes with a database named 'test' that anyone can
  95. access. This is also intended only for testing, and should be removed
  96. before moving into a production environment.
  97. Remove test database and access to it? [Y/n] y
  98. - Dropping test database...
  99. ... Success!
  100. - Removing privileges on test database...
  101. ... Success!
  102. Reloading the privilege tables will ensure that all changes made so far
  103. will take effect immediately.
  104. Reload privilege tables now? [Y/n] y
  105. ... Success!
  106. Cleaning up...
  107. 5. service mysql stop
  108. 6. uncomment all wsrep* lines except first server, where leave only in my.cnf wsrep_cluster_address='gcomm://';
  109. 7. start first node
  110. 8. Start third node which is connected to first one
  111. 9. Start second node which is connected to third one
  112. 10. After starting cluster, it must be change cluster address at first starting node without restart database and change config my.cnf.
  113. .. code-block:: bash
  114. mysql> SET GLOBAL wsrep_cluster_address='gcomm://10.0.0.2';
  115. Read more
  116. =========
  117. * https://github.com/CaptTofu/ansible-galera
  118. * http://www.sebastien-han.fr/blog/2012/04/15/active-passive-failover-cluster-on-a-mysql-galera-cluster-with-haproxy-lsb-agent/
  119. * http://opentodo.net/2012/12/mysql-multi-master-replication-with-galera/
  120. * http://www.codership.com/wiki/doku.php
  121. * Best one: - http://www.sebastien-han.fr/blog/2012/04/01/mysql-multi-master-replication-with-galera/
  122. Documentation and Bugs
  123. ======================
  124. To learn how to install and update salt-formulas, consult the documentation
  125. available online at:
  126. http://salt-formulas.readthedocs.io/
  127. In the unfortunate event that bugs are discovered, they should be reported to
  128. the appropriate issue tracker. Use Github issue tracker for specific salt
  129. formula:
  130. https://github.com/salt-formulas/salt-formula-galera/issues
  131. For feature requests, bug reports or blueprints affecting entire ecosystem,
  132. use Launchpad salt-formulas project:
  133. https://launchpad.net/salt-formulas
  134. You can also join salt-formulas-users team and subscribe to mailing list:
  135. https://launchpad.net/~salt-formulas-users
  136. Developers wishing to work on the salt-formulas projects should always base
  137. their work on master branch and submit pull request against specific formula.
  138. https://github.com/salt-formulas/salt-formula-galera
  139. Any questions or feedback is always welcome so feel free to join our IRC
  140. channel:
  141. #salt-formulas @ irc.freenode.net