{"id":8908,"date":"2022-02-25T17:49:40","date_gmt":"2022-02-25T16:49:40","guid":{"rendered":"https:\/\/blog.capdata.fr\/?p=8908"},"modified":"2022-02-25T17:54:59","modified_gmt":"2022-02-25T16:54:59","slug":"migrer-dun-cluster-galera-mariadb-10-3-vers-mariadb-10-5-avec-la-replication-logique","status":"publish","type":"post","link":"https:\/\/blog.capdata.fr\/index.php\/migrer-dun-cluster-galera-mariadb-10-3-vers-mariadb-10-5-avec-la-replication-logique\/","title":{"rendered":"Migrer d’un cluster Galera MariaDB 10.3 vers MariaDB 10.5 avec la r\u00e9plication logique"},"content":{"rendered":"\"twitter\"<\/a>\"linkedin\"<\/a>\"mail\"<\/a>

Suite de l’\u00e9pisode pr\u00e9c\u00e9dent <\/a>… Cette fois nous voulons migrer notre socle Debian 10 \/ MariaDB 10.3 \/ Galera-3 vers le socle Debian 11 \/ MariaDB 10.5 \/ Galera-4, avec un minimum de temps d’indisponibilit\u00e9. Nous pouvons le faire en mettant en place une r\u00e9plication standard MySQL entre les 2 clusters, pour les maintenir synchronis\u00e9s jusqu’\u00e0 la date de bascule sur le nouvel environnement.<\/p>\n\n\n
Disclaimer <\/strong>: attention on va simplement montrer le principe de superposer une r\u00e9plication logique par dessus une r\u00e9plication synchrone Galera, pour maintenir en phase deux clusters disjoints. On utilisera directement les IP plut\u00f4t que des noms DNS, etc… le but n’est pas de faire une proc\u00e9dure de migration nette et sans bavures, mais bien de d\u00e9montrer un concept pour montrer que c’est possible. Donc \u00e0 adapter selon vos besoins et contraintes…<\/strong><\/i><\/i><\/td>\n<\/tr>\n<\/table>\n

La cible attendue : <\/p>\n

\"\"<\/p>\n

…et ma config LXC au d\u00e9part :<\/p>\n

\r\nroot@ubuntu20:~# lxc list\r\n+----------+---------+-----------------------+-----------------------------------------------+-----------+-----------+\r\n|   NAME   |  STATE  |         IPV4          |                     IPV6                      |   TYPE    | SNAPSHOTS |\r\n+----------+---------+-----------------------+-----------------------------------------------+-----------+-----------+\r\n| galera1  | RUNNING | 10.186.157.38 (eth0)  | fd42:a4e7:fd78:5160:216:3eff:fe16:1ebf (eth0) | CONTAINER | 0         |\r\n+----------+---------+-----------------------+-----------------------------------------------+-----------+-----------+\r\n| galera2  | RUNNING | 10.186.157.242 (eth0) | fd42:a4e7:fd78:5160:216:3eff:fee3:1939 (eth0) | CONTAINER | 0         |\r\n+----------+---------+-----------------------+-----------------------------------------------+-----------+-----------+\r\n| galera3  | RUNNING | 10.186.157.196 (eth0) | fd42:a4e7:fd78:5160:216:3eff:fe4f:893e (eth0) | CONTAINER | 0         |\r\n+----------+---------+-----------------------+-----------------------------------------------+-----------+-----------+\r\n| galera4  | RUNNING | 10.186.157.206 (eth0) | fd42:a4e7:fd78:5160:216:3eff:fe0d:ef85 (eth0) | CONTAINER | 0         |\r\n+----------+---------+-----------------------+-----------------------------------------------+-----------+-----------+\r\n| galera5  | RUNNING | 10.186.157.207 (eth0) | fd42:a4e7:fd78:5160:216:3eff:fe9c:5a7c (eth0) | CONTAINER | 0         |\r\n+----------+---------+-----------------------+-----------------------------------------------+-----------+-----------+\r\n| galera6  | RUNNING | 10.186.157.208 (eth0) | fd42:a4e7:fd78:5160:216:3eff:fe22:ab44 (eth0) | CONTAINER | 0         |\r\n+----------+---------+-----------------------+-----------------------------------------------+-----------+-----------+\r\n| galerarb | STOPPED |                       |                                               | CONTAINER | 0         |\r\n+----------+---------+-----------------------+-----------------------------------------------+-----------+-----------+\r\n<\/pre>\n
Nous partons du principe que nous avons d\u00e9j\u00e0 configur\u00e9 un cluster vierge en MariaDB 10.5\/Galera-4. Il faudra penser \u00e0 affecter des @@server_id diff\u00e9rents pour les 3 noeuds cible, qui pourront \u00eatre red\u00e9marr\u00e9s un \u00e0 un. <\/p>\n
Autre remarque, nous n’utiliserons pas l’arbitre dans ce type de migration. A noter qu’un arbitre serait n\u00e9cessaire dans le cas d’un rolling upgrade<\/a> in-place en migrant les noeuds un par un, mais il  y a plusieurs contraintes, il faut suivre le chemin de migration de MariaDB (\u00e9viter de sauter de version) dans ce cas, et on n’aura pas de retour arri\u00e8re si \u00e7a se passe mal une fois la migration termin\u00e9e. <\/p>\n
Cr\u00e9ation de l’utilisateur de r\u00e9plication<\/h2>\n
Il sera utilis\u00e9 par galera4 pour se connecter \u00e0 galera1 et recopier les log binaires dans ses relaylogs locaux.<\/p>\n
\r\nMariaDB [(none)]> create user 'repl'@'10.186.157.206' identified by '********' ;\r\nQuery OK, 0 rows affected (0.009 sec)\r\n\r\nMariaDB [(none)]> grant replication slave on *.* to 'repl'@'10.186.157.206' ;\r\nQuery OK, 0 rows affected (0.008 sec)\r\n\r\nMariaDB [(none)]> flush privileges ;\r\nQuery OK, 0 rows affected (0.008 sec)\r\n\r\nMariaDB [(none)]> show grants for 'repl'@'10.186.157.206' ;\r\n+------------------------------------------------------------------------------------------------------------------------------+\r\n| Grants for repl@10.186.157.206                                                                                               |\r\n+------------------------------------------------------------------------------------------------------------------------------+\r\n| GRANT REPLICATION SLAVE ON *.* TO `repl`@`10.186.157.206` IDENTIFIED BY PASSWORD '*64ABE8A05EC109FED93AF1865B498359DC3B80E8' |\r\n+------------------------------------------------------------------------------------------------------------------------------+\r\n1 row in set (0.002 sec)\r\n<\/pre>\n
Eventuellement un test de connexion depuis galera4 pour \u00e9viter les surprises:<\/p>\n
\r\nroot@galera4:~# mysql --user=repl --host=10.186.157.38 \\\r\n--port=3306 --password --execute='select version();'\r\nEnter password: \r\n+--------------------------------------------+\r\n| version()                                  |\r\n+--------------------------------------------+\r\n| 10.3.34-MariaDB-1:10.3.34+maria~buster-log |\r\n+--------------------------------------------+\r\n<\/pre>\n
OK<\/p>\n
Synchronisation entre les 2 clusters<\/h2>\n
Evidemment ici la base sakila nous permet d’utiliser mysqldump pour faire la synchro. Nous allons injecter directement le dump dans le noeud galera4 du second cluster, le tout sera automatiquement r\u00e9pliqu\u00e9 sur les 2 autres noeuds galera5 et galera6. <\/p>\n
\r\nroot@galera1:\/mariabackup# mysqldump --user=root \\\r\n--socket=\/var\/run\/mysqld\/mysqld.sock \\\r\n--password --flush-logs --single-transaction \\\r\n--master-data=2 sakila | gzip > sakila.UPGRADE-105.dmp.gz  \r\nEnter password: \r\n<\/pre>\n
Puis transfert vers galera4…dans mon cas avec lxd:<\/p>\n
\r\nroot@ubuntu20:~# lxc file pull galera1\/mariabackup\/sakila.UPGRADE-105.dmp.gz .\r\nroot@ubuntu20:~# lxc file push sakila.UPGRADE-105.dmp.gz galera4\/mariabackup\/sakila.UPGRADE-105.dmp.gz\r\n<\/pre>\n
A noter que je choisis ici de ne sauvegarder que la base sakila. Je n’ai pas d’autre base m\u00e9tier sur mon cluster en 10.3. S’il y en avait d’autres, il faudrait les ajouter dans le dump. <\/p>\n
On n’utilisera pas non plus un binlog_do_db \/ replicate_do_db<\/a> pour filtrer en amont ou en aval dans les binlogs, car en raison de l’ambig\u00fcit\u00e9 li\u00e9e au contexte de la mise \u00e0 jour, on ne veut pas prendre le risque de rater une mise \u00e0 jour qui ne se ferait pas dans le contexte de la base.  Peut \u00eatre un article bient\u00f4t pour expliquer ce ph\u00e9nom\u00e8ne…<\/p>\n
Avant de recharger, on va noter le binlog et la position qui ont \u00e9t\u00e9 renseign\u00e9es au d\u00e9but du dump. En mettant 2 \u00e0 –master-data<\/em>, la commande reste en commentaires dans le dump, on choisit de l’appliquer une fois le dump int\u00e9gr\u00e9:<\/p>\n
\r\nroot@galera4:\/mariabackup# gzip -d sakila.UPGRADE-105.dmp.gz \r\nroot@galera4:\/mariabackup# grep -i "change master" sakila.UPGRADE-105.dmp \r\n-- CHANGE MASTER TO MASTER_LOG_FILE='mariadb-bin.000051', MASTER_LOG_POS=389;\r\n<\/pre>\n
OK nous n’avons pas demand\u00e9 \u00e0 mysqldump de pr\u00e9ciser l’ordre de cr\u00e9ation de la base, donc il faut la recr\u00e9er \u00e0 la main, et charger le backup. En fonction de la taille de celui-ci, cela peut prendre un certain temps:<\/p>\n
\r\nMariaDB [(none)]> create database sakila ;\r\nQuery OK, 1 row affected (0.013 sec)\r\n<\/pre>\n
\r\nroot@galera4:\/mariabackup# time mysql sakila < sakila.UPGRADE-105.dmp \r\n\r\nreal\t0m4.861s\r\nuser\t0m0.188s\r\nsys\t0m0.033s\r\n<\/pre>\n
Enfin on passe le CHANGE MASTER TO<\/em> et on peut d\u00e9marrer les slaves : <\/p>\n
\r\nMariaDB [(none)]> CHANGE MASTER TO \r\n    -> MASTER_HOST="10.186.157.38",\r\n    -> MASTER_PORT=3306,\r\n    -> MASTER_USER="repl",\r\n    -> MASTER_PASSWORD="******",\r\n    -> MASTER_LOG_FILE="mariadb-bin.000051",\r\n    -> MASTER_LOG_POS=389; \r\n\r\nMariaDB [(none)]> start slave; \r\nQuery OK, 0 rows affected (0.001 sec)\r\n\r\nMariaDB [(none)]> show slave status \\G\r\n*************************** 1. row ***************************\r\n                Slave_IO_State: Waiting for master to send event\r\n                   Master_Host: 10.186.157.38\r\n                   Master_User: repl\r\n                   Master_Port: 3306\r\n                 Connect_Retry: 60\r\n               Master_Log_File: mariadb-bin.000051\r\n           Read_Master_Log_Pos: 734\r\n                Relay_Log_File: mysqld-relay-bin.000002\r\n                 Relay_Log_Pos: 902\r\n         Relay_Master_Log_File: mariadb-bin.000051\r\n              Slave_IO_Running: Yes\r\n             Slave_SQL_Running: Yes\r\n               Replicate_Do_DB: \r\n           Replicate_Ignore_DB: \r\n            Replicate_Do_Table: \r\n        Replicate_Ignore_Table: \r\n       Replicate_Wild_Do_Table: \r\n   Replicate_Wild_Ignore_Table: \r\n                    Last_Errno: 0\r\n                    Last_Error: \r\n                  Skip_Counter: 0\r\n           Exec_Master_Log_Pos: 734\r\n               Relay_Log_Space: 1212\r\n               Until_Condition: None\r\n                Until_Log_File: \r\n                 Until_Log_Pos: 0\r\n            Master_SSL_Allowed: No\r\n            Master_SSL_CA_File: \r\n            Master_SSL_CA_Path: \r\n               Master_SSL_Cert: \r\n             Master_SSL_Cipher: \r\n                Master_SSL_Key: \r\n         Seconds_Behind_Master: 0\r\n Master_SSL_Verify_Server_Cert: No\r\n                 Last_IO_Errno: 0\r\n                 Last_IO_Error: \r\n                Last_SQL_Errno: 0\r\n                Last_SQL_Error: \r\n   Replicate_Ignore_Server_Ids: \r\n              Master_Server_Id: 1\r\n                Master_SSL_Crl: \r\n            Master_SSL_Crlpath: \r\n                    Using_Gtid: No\r\n                   Gtid_IO_Pos: \r\n       Replicate_Do_Domain_Ids: \r\n   Replicate_Ignore_Domain_Ids: \r\n                 Parallel_Mode: optimistic\r\n                     SQL_Delay: 0\r\n           SQL_Remaining_Delay: NULL\r\n       Slave_SQL_Running_State: Slave has read all relay log; waiting for more updates\r\n              Slave_DDL_Groups: 1\r\nSlave_Non_Transactional_Groups: 0\r\n    Slave_Transactional_Groups: 1\r\n1 row in set (0.000 sec)\r\n<\/pre>\n
OK tout est bon \u00e0 priori. On peut injecter un peu de donn\u00e9es depuis galera1 pour valider le bon fonctionnement de la r\u00e9plication sur les autres noeuds du nouveau cluster :<\/p>\n
\r\nMariaDB [(none)]> use sakila ;\r\nReading table information for completion of table and column names\r\nYou can turn off this feature to get a quicker startup with -A\r\n\r\nDatabase changed\r\nMariaDB [sakila]> create table test(a int); \r\nQuery OK, 0 rows affected (0.015 sec)\r\n\r\nMariaDB [sakila]> insert into test values (1) ;\r\nQuery OK, 1 row affected (0.006 sec)\r\n<\/pre>\n
Et v\u00e9rifier sur les 3 noeuds en 10.5:<\/p>\n
\r\n-- Sur galera4, 5 ou 6\r\nroot@ubuntu20:~# for srv in galera4 galera5 galera6\r\n> do\r\n> lxc exec ${srv} -- mysql --execute="select * from sakila.test ;"\r\n> done\r\n+------+\r\n| a    |\r\n+------+\r\n|    1 |\r\n+------+\r\n+------+\r\n| a    |\r\n+------+\r\n|    1 |\r\n+------+\r\n+------+\r\n| a    |\r\n+------+\r\n|    1 |\r\n+------+\r\n<\/pre>\n
Donc \u00e0 partir de l\u00e0, nous avons deux clusters diff\u00e9rents qui sont maintenus synchrones l’un avec l’autre, noter qu’il n’y a eu besoin d’aucune interruption de service (je n’ai pas chang\u00e9 le @@server_id sur galera1) pour mettre en place la r\u00e9plication.
\nLa bascule sur la nouvelle version consistera donc \u00e0 simplement stopper les applications, laisser les transactions se r\u00e9pliquer sur le cluster en 10.5, et une fois le master et le slave en phase, stopper les slaves et basculer les applications sur le nouveau cluster. <\/p>\n
Bon week-end \u00e0 toutes et tous !
\n~David <\/p>\n\"twitter\"<\/a>\"linkedin\"<\/a>\"mail\"<\/a>","protected":false},"excerpt":{"rendered":"
Suite de l’\u00e9pisode pr\u00e9c\u00e9dent … Cette fois nous voulons migrer notre socle Debian 10 \/ MariaDB 10.3 \/ Galera-3 vers le socle Debian 11 \/ MariaDB 10.5 \/ Galera-4, avec un minimum de temps d’indisponibilit\u00e9. Nous pouvons le faire en… Continuer la lecture →<\/span><\/a><\/p>\n","protected":false},"author":2,"featured_media":8912,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[383,4,1],"tags":[21,385,137],"class_list":["post-8908","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-container","category-mysql","category-non-classe","tag-cluster","tag-galera","tag-migration"],"yoast_head":"\nMigrer d'un cluster Galera MariaDB 10.3 vers MariaDB 10.5 avec la r\u00e9plication logique - Capdata TECH BLOG<\/title>\n<meta name=\"robots\" content=\"index, follow, max-snippet:-1, max-image-preview:large, max-video-preview:-1\" \/>\n<link rel=\"canonical\" href=\"https:\/\/blog.capdata.fr\/index.php\/migrer-dun-cluster-galera-mariadb-10-3-vers-mariadb-10-5-avec-la-replication-logique\/\" \/>\n<meta property=\"og:locale\" content=\"fr_FR\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"Migrer d'un cluster Galera MariaDB 10.3 vers MariaDB 10.5 avec la r\u00e9plication logique - Capdata TECH BLOG\" \/>\n<meta property=\"og:description\" content=\"Suite de l’\u00e9pisode pr\u00e9c\u00e9dent … Cette fois nous voulons migrer notre socle Debian 10 \/ MariaDB 10.3 \/ Galera-3 vers le socle Debian 11 \/ MariaDB 10.5 \/ Galera-4, avec un minimum de temps d’indisponibilit\u00e9. Nous pouvons le faire en… Continuer la lecture →\" \/>\n<meta property=\"og:url\" content=\"https:\/\/blog.capdata.fr\/index.php\/migrer-dun-cluster-galera-mariadb-10-3-vers-mariadb-10-5-avec-la-replication-logique\/\" \/>\n<meta property=\"og:site_name\" content=\"Capdata TECH BLOG\" \/>\n<meta property=\"article:published_time\" content=\"2022-02-25T16:49:40+00:00\" \/>\n<meta property=\"article:modified_time\" content=\"2022-02-25T16:54:59+00:00\" \/>\n<meta property=\"og:image\" content=\"https:\/\/blog.capdata.fr\/wp-content\/uploads\/2022\/02\/movingin.jpg\" \/>\n\t<meta property=\"og:image:width\" content=\"612\" \/>\n\t<meta property=\"og:image:height\" content=\"408\" \/>\n\t<meta property=\"og:image:type\" content=\"image\/jpeg\" \/>\n<meta name=\"author\" content=\"David Baffaleuf\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:label1\" content=\"\u00c9crit par\" \/>\n\t<meta name=\"twitter:data1\" content=\"David Baffaleuf\" \/>\n\t<meta name=\"twitter:label2\" content=\"Dur\u00e9e de lecture estim\u00e9e\" \/>\n\t<meta name=\"twitter:data2\" content=\"7 minutes\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\/\/schema.org\",\"@graph\":[{\"@type\":\"Article\",\"@id\":\"https:\/\/blog.capdata.fr\/index.php\/migrer-dun-cluster-galera-mariadb-10-3-vers-mariadb-10-5-avec-la-replication-logique\/#article\",\"isPartOf\":{\"@id\":\"https:\/\/blog.capdata.fr\/index.php\/migrer-dun-cluster-galera-mariadb-10-3-vers-mariadb-10-5-avec-la-replication-logique\/\"},\"author\":{\"name\":\"David Baffaleuf\",\"@id\":\"https:\/\/blog.capdata.fr\/#\/schema\/person\/136297da9f61d6e4878abe0f48bc5fbf\"},\"headline\":\"Migrer d’un cluster Galera MariaDB 10.3 vers MariaDB 10.5 avec la r\u00e9plication logique\",\"datePublished\":\"2022-02-25T16:49:40+00:00\",\"dateModified\":\"2022-02-25T16:54:59+00:00\",\"mainEntityOfPage\":{\"@id\":\"https:\/\/blog.capdata.fr\/index.php\/migrer-dun-cluster-galera-mariadb-10-3-vers-mariadb-10-5-avec-la-replication-logique\/\"},\"wordCount\":1420,\"commentCount\":0,\"publisher\":{\"@id\":\"https:\/\/blog.capdata.fr\/#organization\"},\"keywords\":[\"cluster\",\"galera\",\"migration\"],\"articleSection\":[\"Container\",\"MySQL\"],\"inLanguage\":\"fr-FR\",\"potentialAction\":[{\"@type\":\"CommentAction\",\"name\":\"Comment\",\"target\":[\"https:\/\/blog.capdata.fr\/index.php\/migrer-dun-cluster-galera-mariadb-10-3-vers-mariadb-10-5-avec-la-replication-logique\/#respond\"]}]},{\"@type\":\"WebPage\",\"@id\":\"https:\/\/blog.capdata.fr\/index.php\/migrer-dun-cluster-galera-mariadb-10-3-vers-mariadb-10-5-avec-la-replication-logique\/\",\"url\":\"https:\/\/blog.capdata.fr\/index.php\/migrer-dun-cluster-galera-mariadb-10-3-vers-mariadb-10-5-avec-la-replication-logique\/\",\"name\":\"Migrer d'un cluster Galera MariaDB 10.3 vers MariaDB 10.5 avec la r\u00e9plication logique - Capdata TECH BLOG\",\"isPartOf\":{\"@id\":\"https:\/\/blog.capdata.fr\/#website\"},\"datePublished\":\"2022-02-25T16:49:40+00:00\",\"dateModified\":\"2022-02-25T16:54:59+00:00\",\"breadcrumb\":{\"@id\":\"https:\/\/blog.capdata.fr\/index.php\/migrer-dun-cluster-galera-mariadb-10-3-vers-mariadb-10-5-avec-la-replication-logique\/#breadcrumb\"},\"inLanguage\":\"fr-FR\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\/\/blog.capdata.fr\/index.php\/migrer-dun-cluster-galera-mariadb-10-3-vers-mariadb-10-5-avec-la-replication-logique\/\"]}]},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\/\/blog.capdata.fr\/index.php\/migrer-dun-cluster-galera-mariadb-10-3-vers-mariadb-10-5-avec-la-replication-logique\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Accueil\",\"item\":\"https:\/\/blog.capdata.fr\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"Migrer d’un cluster Galera MariaDB 10.3 vers MariaDB 10.5 avec la r\u00e9plication logique\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\/\/blog.capdata.fr\/#website\",\"url\":\"https:\/\/blog.capdata.fr\/\",\"name\":\"Capdata TECH BLOG\",\"description\":\"Le blog technique sur les bases de donn\u00e9es de CAP DATA Consulting\",\"publisher\":{\"@id\":\"https:\/\/blog.capdata.fr\/#organization\"},\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\/\/blog.capdata.fr\/?s={search_term_string}\"},\"query-input\":\"required name=search_term_string\"}],\"inLanguage\":\"fr-FR\"},{\"@type\":\"Organization\",\"@id\":\"https:\/\/blog.capdata.fr\/#organization\",\"name\":\"Capdata TECH BLOG\",\"url\":\"https:\/\/blog.capdata.fr\/\",\"logo\":{\"@type\":\"ImageObject\",\"inLanguage\":\"fr-FR\",\"@id\":\"https:\/\/blog.capdata.fr\/#\/schema\/logo\/image\/\",\"url\":\"https:\/\/blog.capdata.fr\/wp-content\/uploads\/2023\/01\/logo_capdata.webp\",\"contentUrl\":\"https:\/\/blog.capdata.fr\/wp-content\/uploads\/2023\/01\/logo_capdata.webp\",\"width\":800,\"height\":254,\"caption\":\"Capdata TECH BLOG\"},\"image\":{\"@id\":\"https:\/\/blog.capdata.fr\/#\/schema\/logo\/image\/\"},\"sameAs\":[\"https:\/\/www.linkedin.com\/company\/cap-data-consulting\/mycompany\/\"]},{\"@type\":\"Person\",\"@id\":\"https:\/\/blog.capdata.fr\/#\/schema\/person\/136297da9f61d6e4878abe0f48bc5fbf\",\"name\":\"David Baffaleuf\",\"sameAs\":[\"http:\/\/www.capdata.fr\"],\"url\":\"https:\/\/blog.capdata.fr\/index.php\/author\/dbaffaleuf\/\"}]}<\/script>\n<!-- \/ Yoast SEO plugin. -->","yoast_head_json":{"title":"Migrer d'un cluster Galera MariaDB 10.3 vers MariaDB 10.5 avec la r\u00e9plication logique - Capdata TECH BLOG","robots":{"index":"index","follow":"follow","max-snippet":"max-snippet:-1","max-image-preview":"max-image-preview:large","max-video-preview":"max-video-preview:-1"},"canonical":"https:\/\/blog.capdata.fr\/index.php\/migrer-dun-cluster-galera-mariadb-10-3-vers-mariadb-10-5-avec-la-replication-logique\/","og_locale":"fr_FR","og_type":"article","og_title":"Migrer d'un cluster Galera MariaDB 10.3 vers MariaDB 10.5 avec la r\u00e9plication logique - Capdata TECH BLOG","og_description":"Suite de l’\u00e9pisode pr\u00e9c\u00e9dent … Cette fois nous voulons migrer notre socle Debian 10 \/ MariaDB 10.3 \/ Galera-3 vers le socle Debian 11 \/ MariaDB 10.5 \/ Galera-4, avec un minimum de temps d’indisponibilit\u00e9. Nous pouvons le faire en… Continuer la lecture →","og_url":"https:\/\/blog.capdata.fr\/index.php\/migrer-dun-cluster-galera-mariadb-10-3-vers-mariadb-10-5-avec-la-replication-logique\/","og_site_name":"Capdata TECH BLOG","article_published_time":"2022-02-25T16:49:40+00:00","article_modified_time":"2022-02-25T16:54:59+00:00","og_image":[{"width":612,"height":408,"url":"https:\/\/blog.capdata.fr\/wp-content\/uploads\/2022\/02\/movingin.jpg","type":"image\/jpeg"}],"author":"David Baffaleuf","twitter_card":"summary_large_image","twitter_misc":{"\u00c9crit par":"David Baffaleuf","Dur\u00e9e de lecture estim\u00e9e":"7 minutes"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"Article","@id":"https:\/\/blog.capdata.fr\/index.php\/migrer-dun-cluster-galera-mariadb-10-3-vers-mariadb-10-5-avec-la-replication-logique\/#article","isPartOf":{"@id":"https:\/\/blog.capdata.fr\/index.php\/migrer-dun-cluster-galera-mariadb-10-3-vers-mariadb-10-5-avec-la-replication-logique\/"},"author":{"name":"David Baffaleuf","@id":"https:\/\/blog.capdata.fr\/#\/schema\/person\/136297da9f61d6e4878abe0f48bc5fbf"},"headline":"Migrer d’un cluster Galera MariaDB 10.3 vers MariaDB 10.5 avec la r\u00e9plication logique","datePublished":"2022-02-25T16:49:40+00:00","dateModified":"2022-02-25T16:54:59+00:00","mainEntityOfPage":{"@id":"https:\/\/blog.capdata.fr\/index.php\/migrer-dun-cluster-galera-mariadb-10-3-vers-mariadb-10-5-avec-la-replication-logique\/"},"wordCount":1420,"commentCount":0,"publisher":{"@id":"https:\/\/blog.capdata.fr\/#organization"},"keywords":["cluster","galera","migration"],"articleSection":["Container","MySQL"],"inLanguage":"fr-FR","potentialAction":[{"@type":"CommentAction","name":"Comment","target":["https:\/\/blog.capdata.fr\/index.php\/migrer-dun-cluster-galera-mariadb-10-3-vers-mariadb-10-5-avec-la-replication-logique\/#respond"]}]},{"@type":"WebPage","@id":"https:\/\/blog.capdata.fr\/index.php\/migrer-dun-cluster-galera-mariadb-10-3-vers-mariadb-10-5-avec-la-replication-logique\/","url":"https:\/\/blog.capdata.fr\/index.php\/migrer-dun-cluster-galera-mariadb-10-3-vers-mariadb-10-5-avec-la-replication-logique\/","name":"Migrer d'un cluster Galera MariaDB 10.3 vers MariaDB 10.5 avec la r\u00e9plication logique - Capdata TECH BLOG","isPartOf":{"@id":"https:\/\/blog.capdata.fr\/#website"},"datePublished":"2022-02-25T16:49:40+00:00","dateModified":"2022-02-25T16:54:59+00:00","breadcrumb":{"@id":"https:\/\/blog.capdata.fr\/index.php\/migrer-dun-cluster-galera-mariadb-10-3-vers-mariadb-10-5-avec-la-replication-logique\/#breadcrumb"},"inLanguage":"fr-FR","potentialAction":[{"@type":"ReadAction","target":["https:\/\/blog.capdata.fr\/index.php\/migrer-dun-cluster-galera-mariadb-10-3-vers-mariadb-10-5-avec-la-replication-logique\/"]}]},{"@type":"BreadcrumbList","@id":"https:\/\/blog.capdata.fr\/index.php\/migrer-dun-cluster-galera-mariadb-10-3-vers-mariadb-10-5-avec-la-replication-logique\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Accueil","item":"https:\/\/blog.capdata.fr\/"},{"@type":"ListItem","position":2,"name":"Migrer d’un cluster Galera MariaDB 10.3 vers MariaDB 10.5 avec la r\u00e9plication logique"}]},{"@type":"WebSite","@id":"https:\/\/blog.capdata.fr\/#website","url":"https:\/\/blog.capdata.fr\/","name":"Capdata TECH BLOG","description":"Le blog technique sur les bases de donn\u00e9es de CAP DATA Consulting","publisher":{"@id":"https:\/\/blog.capdata.fr\/#organization"},"potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/blog.capdata.fr\/?s={search_term_string}"},"query-input":"required name=search_term_string"}],"inLanguage":"fr-FR"},{"@type":"Organization","@id":"https:\/\/blog.capdata.fr\/#organization","name":"Capdata TECH BLOG","url":"https:\/\/blog.capdata.fr\/","logo":{"@type":"ImageObject","inLanguage":"fr-FR","@id":"https:\/\/blog.capdata.fr\/#\/schema\/logo\/image\/","url":"https:\/\/blog.capdata.fr\/wp-content\/uploads\/2023\/01\/logo_capdata.webp","contentUrl":"https:\/\/blog.capdata.fr\/wp-content\/uploads\/2023\/01\/logo_capdata.webp","width":800,"height":254,"caption":"Capdata TECH BLOG"},"image":{"@id":"https:\/\/blog.capdata.fr\/#\/schema\/logo\/image\/"},"sameAs":["https:\/\/www.linkedin.com\/company\/cap-data-consulting\/mycompany\/"]},{"@type":"Person","@id":"https:\/\/blog.capdata.fr\/#\/schema\/person\/136297da9f61d6e4878abe0f48bc5fbf","name":"David Baffaleuf","sameAs":["http:\/\/www.capdata.fr"],"url":"https:\/\/blog.capdata.fr\/index.php\/author\/dbaffaleuf\/"}]}},"_links":{"self":[{"href":"https:\/\/blog.capdata.fr\/index.php\/wp-json\/wp\/v2\/posts\/8908","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/blog.capdata.fr\/index.php\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/blog.capdata.fr\/index.php\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/blog.capdata.fr\/index.php\/wp-json\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/blog.capdata.fr\/index.php\/wp-json\/wp\/v2\/comments?post=8908"}],"version-history":[{"count":2,"href":"https:\/\/blog.capdata.fr\/index.php\/wp-json\/wp\/v2\/posts\/8908\/revisions"}],"predecessor-version":[{"id":8911,"href":"https:\/\/blog.capdata.fr\/index.php\/wp-json\/wp\/v2\/posts\/8908\/revisions\/8911"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/blog.capdata.fr\/index.php\/wp-json\/wp\/v2\/media\/8912"}],"wp:attachment":[{"href":"https:\/\/blog.capdata.fr\/index.php\/wp-json\/wp\/v2\/media?parent=8908"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/blog.capdata.fr\/index.php\/wp-json\/wp\/v2\/categories?post=8908"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/blog.capdata.fr\/index.php\/wp-json\/wp\/v2\/tags?post=8908"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}