Merge pull request #8 from michel-silva/fix-mysqldump-master-database

Fix mysqldump master database
bitnami · Feb 7, 2024 · 5f7f32f · 5f7f32f
2 parents 4e65ce4 + 475de9f
commit 5f7f32f
Show file tree

Hide file tree

Showing 2 changed files with 2 additions and 2 deletions.
diff --git a/bitnami/mysql/README.md b/bitnami/mysql/README.md
@@ -422,7 +422,7 @@ The above command scales up the number of slaves to `3`. You can scale down in t
 
 > **Note**: You should not scale up/down the number of master nodes. Always have only one master node running.
 
-If your master database is missing some binary files, the replication will break. It's possible to add `MYSQL_REPLICATION_SLAVE_DUMP=true` to make a dump on the master and import it on the slave.
+If your master database missing some binary files, the replication will broken. It's possible add `MYSQL_REPLICATION_SLAVE_DUMP=true` toe make a dump on master and import it on slave.
 
 > **Note**: The master database must be only used by this process until the end to avoid missing data.
 

diff --git a/bitnami/mysql/docker-compose-replication.yml b/bitnami/mysql/docker-compose-replication.yml
@@ -40,7 +40,7 @@ services:
       - MYSQL_MASTER_ROOT_PASSWORD=my_root_password
       # ALLOW_EMPTY_PASSWORD is recommended only for development.
       - ALLOW_EMPTY_PASSWORD=yes
-      # In case of missing binary files on master, use `true` to reset those binary files. Creating a previous backup is recommended.
+      # Only use true if master node missing binary files (The binary files will be reset, recomendate backup files)
       - MYSQL_REPLICATION_SLAVE_DUMP=false
     healthcheck:
       test: ['CMD', '/opt/bitnami/scripts/mysql/healthcheck.sh']