Les deux révisions précédentesRévision précédenteProchaine révision | Révision précédenteProchaine révisionLes deux révisions suivantes |
informatique:sgbd:mysql [21/03/2021 11:28] – [Replication] cyrille | informatique:sgbd:mysql [21/03/2021 12:02] – [Replication] cyrille |
---|
| |
===== Replication ===== | ===== Replication ===== |
| |
| [[/informatique/sgbd/mysql/replication|mysql/replication]] |
| |
Articles: | Articles: |
* [[https://opensolitude.com/2016/09/12/painless-high-availability-failover-mariadb.html|Painless HA failover with MariaDB]] (2016 | * [[https://opensolitude.com/2016/09/12/painless-high-availability-failover-mariadb.html|Painless HA failover with MariaDB]] (2016 |
* avec Master<->Master | * avec Master<->Master |
* ''auto_increment_increment'' and ''auto_increment_offset' variables such that one only uses odd numbers for auto-incrementing integer primary keys and the other use even bumbers | * ''auto_increment_increment'' and ''auto_increment_offset'' variables such that one only uses odd numbers for auto-incrementing integer primary keys and the other use even bumbers |
* [[https://fr.wikibooks.org/wiki/MySQL/Réplication|MySQL/Réplication]] | * [[https://fr.wikibooks.org/wiki/MySQL/R%C3%A9plication|MySQL Réplication]] |
* [[https://www.christophe-casalegno.com/reparation-dune-replication-mysql-mariadb/|Réparation d’une réplication MySQL ou MariaDB]] | * [[https://www.christophe-casalegno.com/reparation-dune-replication-mysql-mariadb/|Réparation d’une réplication MySQL ou MariaDB]] |
* [[http://missingmanuals.com/pub/a/onlamp/2006/04/20/advanced-mysql-replication.html?page=1|Advanced MySQL Replication Techniques]] (2006-04-20) | * [[http://missingmanuals.com/pub/a/onlamp/2006/04/20/advanced-mysql-replication.html?page=1|Advanced MySQL Replication Techniques]] (2006-04-20) |
* [[http://www.ovaistariq.net/528/statement-based-vs-row-based-replication/|Statement-based vs Row-based Replication]] (2011-01) | * [[http://www.ovaistariq.net/528/statement-based-vs-row-based-replication/|Statement-based vs Row-based Replication]] (2011-01) |
| |
| ==== Reprise après échec/panne ==== |
| |
Sans arrêter le Master avec l'option "--master-data" de mysqldump. | Sans arrêter le Master avec l'option "--master-data" de mysqldump. |
* http://dev.mysql.com/doc/refman/5.1/en/replication-howto-mysqldump.html | * http://dev.mysql.com/doc/refman/5.1/en/replication-howto-mysqldump.html |
| |
TODO : | ==== Superviser la réplication ==== |
| |
* replication check ? | * replication check ? |
* [[https://mariadb.com/kb/en/show-replica-status/|show slave status]] (ou SHOW REPLICA] | * [[https://mariadb.com/kb/en/show-replica-status/|show slave status]] (ou SHOW REPLICA] |
* SHOW PROCESSLIST; SHOW SLAVE HOSTS; | * SHOW PROCESSLIST; SHOW SLAVE HOSTS; |
| |
| Dans ''/var/log/syslog'' des lignes comme ''...mysqld[123]: 101015 21:11:19 [ERROR] Slave: Error...'' |
| |
| |
| |
* [[http://www.mysqlperformanceblog.com/2007/11/01/innodb-performance-optimization-basics|Innodb Performance Optimization Basics]] sur mysqlperformanceblog.com | * [[http://www.mysqlperformanceblog.com/2007/11/01/innodb-performance-optimization-basics|Innodb Performance Optimization Basics]] sur mysqlperformanceblog.com |
| * [[https://fr.wikibooks.org/wiki/MySQL/Optimisation|MySQL/Optimisation]] sur wikibooks |
* [[http://hackmysql.com/selectandsort|MySQL Select and Sort Status Variables]] | * [[http://hackmysql.com/selectandsort|MySQL Select and Sort Status Variables]] |
* [[http://phpinfo.net/articles/article_optimisation-mysql.html|Optimisation MySQL]] Par Laurent DECORPS sur phpinfo.net | * [[http://phpinfo.net/articles/article_optimisation-mysql.html|Optimisation MySQL]] Par Laurent DECORPS sur phpinfo.net |
* With MyISAM tables that have no deleted rows, you can insert rows at the end at the same time that another query is reading from the table. If this is important for you, you should consider using the table in ways that avoid deleting rows. Another possibility is to run **OPTIMIZE TABLE after you have deleted a lot of rows**. | * With MyISAM tables that have no deleted rows, you can insert rows at the end at the same time that another query is reading from the table. If this is important for you, you should consider using the table in ways that avoid deleting rows. Another possibility is to run **OPTIMIZE TABLE after you have deleted a lot of rows**. |
| |
==== Comparaison InnoDB BuiltIn vs Plugin ==== | |
| |
Comparaison tpc-c entre la version embarquée de InnoDB et le plugin InnoDB sur une instance Amazon c1.xlarge et du MySQL 5.1.43. Pas de tuning particulier => +100% !!! | |
* en abscisses, le temps : 20 minutes de mesure avec 10 minutes de chauffe | |
* en ordonnées, le nombre de transactions | |
| |
{{:informatique:sgbd:mysql_comparaison_innodb_plugin-vs-builtin.png|}} | |
| |
Author: [[http://www.dotdeb.org/|GUI]] | |
| |