@@ -41,7 +41,11 @@ ports 7001 and 7002. <h2 id="schemafiles">Schema files</h2> -I'll use the Tigase MySQL schema file as my example schema. +I'll use the +<a href="http://www.tigase.org/" title="tigase.org | Open Source and Free (GPLv3) Jabber/XMPP environment.">Tigase</a> +<a href="http://projects.tigase.org/server/trac/browser/trunk/database/mysql-schema.sql" title="/trunk/database/mysql-schema.sql - Tigase Server - Trac">MySQL schema file +</a> +as my example schema. The sample data I'll insert into the database, are just made up values and probably not even valid from the point of view of Tigase. @@ -64,8 +68,9 @@ different <code>server-id</code>;</li> server.</li> </ul> -For any mysql command to use a specific server, you just need to -add a <code>--defaults-file=$HOWTO_DIR/etc/server-1.cnf</code>. +For any MySQL command to use a specific server, you just need to +add a <code>--defaults-file=$HOWTO_DIR/etc/server-1.cnf</code> (replace 1 with 2 to work +on the second server). <h2 id="starttwoservers">Start two servers</h2> @@ -96,19 +101,19 @@ mysql --defaults-file=$HOWTO_DIR/etc/server-2.cnf -u root Please note that this procedure did not set a <code>root</code> account password. This means that anybody can connect as <code>root</code> to your database. -For production environments it is strongly recommended that you change +For production environments it is strongly recommended that you change the <code>root</code> password, and delete the anonymous accounts. For our tests purposes, we will not do that. <h2 id="createsampledbwithdataonserver1">Create sample db with data on server1</h2> -On server-1, connect as root, and create the user used by the slave: +On <code>server-1</code>, connect as root, and create the user used by the slave: <pre><code>mysql --defaults-file=$HOWTO_DIR/etc/server-1.cnf -u root < $HOWTO_DIR/sql/repl_user.sql </code></pre> -We will also create the test database, and load our test schema: +We will also create the <code>tigasedb</code> database, and load our test schema: <pre><code>mysqladmin --defaults-file=$HOWTO_DIR/etc/server-1.cnf -u root create tigasedb mysql --defaults-file=$HOWTO_DIR/etc/server-1.cnf -u root tigasedb < $HOWTO_DIR/sql/tigase-mysql-schema.sql @@ -125,13 +130,13 @@ insert some data on them to test: We need to obtain the current master replication position, create a stable snapshot of the data. -Connect as root: +Connect as <code>root</code>: <pre><code>mysql --defaults-file=$HOWTO_DIR/etc/server-1.cnf -u root tigasedb </code></pre> This connection must be left open for the rest of this procedure. This -is required to leave the LOCK in place. +is required to leave the <code>LOCK</code> in place. Execute the following statements: @@ -157,8 +162,8 @@ SHOW MASTER STATUS; tigasedb > tigasedb_dump.sql </code></pre> -Now we need to setup the slave. First, create the tigasedb database and -load the dump taken on the master: +Now we need to setup the slave. First, create the <code>tigasedb</code> database and +load the SQL dump from the master: <pre><code>mysqladmin --defaults-file=$HOWTO_DIR/etc/server-2.cnf -u root create tigasedb mysql --defaults-file=$HOWTO_DIR/etc/server-2.cnf -u root tigasedb < tigasedb_dump.sql @@ -167,7 +172,7 @@ mysql --defaults-file=$HOWTO_DIR/etc/server-2.cnf -u root tigasedb < tigasedb You should have the same data on both servers now. To finish the setup, you need to set the other master parameters on the -slave. Connect as root: +slave. Connect as <code>root</code>: <pre><code>mysql --defaults-file=$HOWTO_DIR/etc/server-2.cnf -u root </code></pre> @@ -184,33 +189,34 @@ slave. Connect as root: START SLAVE; </code></pre> -You can now end the server 1 session where the LOCK was created. +You can now end the server-1 session where the <code>LOCK</code> was created. -You should have a proper master/slave relation working between server-1 -and server-2. +You should have a proper master/slave relation working between <code>server-1</code> +and <code>server-2</code>. -If you look at <code>SHOW MASTER STATUS</code> on server-1 and compare to +If you look at <code>SHOW MASTER STATUS</code> on <code>server-1</code> and compare to <code>SHOW SLAVE STATUS\G</code> (use <code>\G</code> query terminator for a more useful layout) -on server-2, you should see the same <code>File</code> and <code>Position</code> on server-1 -as <code>Master_Log_File</code> and <code>Read_Master_Log_Pos</code> on server-2. +on <code>server-2</code>, you should see the same <code>File</code> and <code>Position</code> on <code>server-1</code> +as <code>Master_Log_File</code> and <code>Read_Master_Log_Pos</code> on <code>server-2</code>. To test, insert a new row in the <code>tig_user</code> table. <pre><code>INSERT INTO tig_users (uid, user_id) VALUES (3, 'user3'); </code></pre> -If you SELECT * FROM tig_users on server-2, you should see the <code>user3</code>. +If you <code>SELECT * FROM tig_users</code> on <code>server-2</code>, you should see the +<code>user3</code> row. You can also re-check the <code>SHOW MASTER STATUS</code>/<code>SHOW SLAVE STATUS</code> and compare the <code>File</code>/<code>Position</code>. <h1 id="server2asmaster">Server 2 as Master</h1> -The last step is to set server 2 as master of server 1. +The last step is to set <code>server-2</code> as master of <code>server-1</code>. -<h2 id="beforeweprocedesomecautions">Before we procede, some cautions</h2> +<h2 id="beforeweprocedesomenotes">Before we procede, some notes</h2> -A master/master setup requires some configuration to make <code>AUTO_INCREMENT</code> +A master/master setup requires some configurations to make <code>AUTO_INCREMENT</code> work correctly. Our config files already include the proper <code>auto_increment_increment</code> and @@ -226,18 +232,18 @@ work correctly. It boils down to this: <ul> -<li><code>auto_increment_increment</code> should be equal to the number of masters you have, N;</li> -<li><code>auto_increment_offset</code> should be different, from 1 to N, on each master.</li> +<li><code>auto_increment_increment</code> should be equal to the number of masters you have, <code>N</code>;</li> +<li><code>auto_increment_offset</code> should be different, from 1 to <code>N</code>, on each master.</li> </ul> <h2 id="makeserver1slavetoserver2">Make server 1 slave to server 2</h2> -You need a replication user on server 2. I'll use the same one: +You need a replication user on <code>server-2</code>. We'll use the same one: <pre><code>mysql --defaults-file=$HOWTO_DIR/etc/server-2.cnf -u root < $HOWTO_DIR/sql/repl_user.sql </code></pre> -Connect to server 2, lock tables and record the master position: +Connect to <code>server-2</code>, lock tables and record the master position: <pre><code>mysql --defaults-file=$HOWTO_DIR/etc/server-2.cnf -u root tigasedb @@ -252,12 +258,12 @@ SHOW MASTER STATUS; 1 row in set (0.00 sec) </code></pre> -Then hop over to server 1, and connect as root: +Then hop over to <code>server-1</code>, and connect as <code>root</code>: <pre><code>mysql --defaults-file=$HOWTO_DIR/etc/server-1.cnf -u root tigasedb </code></pre> -Make server 1 a slave with the proper master position: +Make <code>server-1</code> a slave with the proper master position: <pre><code>CHANGE MASTER TO MASTER_HOST='127.0.0.1', @@ -269,24 +275,27 @@ SHOW MASTER STATUS; START SLAVE; </code></pre> -Release the lock on server 2. The easiest way is just quiting the mysql shell. +Release the lock on <code>server-2</code>. The easiest way is just quiting the +<code>mysql</code> shell. -You should have a proper master/master relation working between server-1 -and server-2. +You should have a proper master/master relation working between <code>server-1</code> +and <code>server-2</code>. -If you look at <code>SHOW MASTER STATUS</code> on server-2 and compare to +If you look at <code>SHOW MASTER STATUS</code> on <code>server-2</code> and compare to <code>SHOW SLAVE STATUS\G</code> (use <code>\G</code> query terminator for a more useful layout) -on server-1, you should see the same <code>File</code> and <code>Position</code> on server-2 -as <code>Master_Log_File</code> and <code>Read_Master_Log_Pos</code> on server-1. +on <code>server-1</code>, you should see the same <code>File</code> and <code>Position</code> on <code>server-2</code> +as <code>Master_Log_File</code> and <code>Read_Master_Log_Pos</code> on <code>server-1</code>. -Do the same procedure inverting server-1 and server-2. You should also -see equal values. +Do the same procedure again, but switch <code>server-1</code> with <code>server-2</code>. You +should also see equal values. <h2 id="finaltests">Final tests</h2> -I recommend that you start two new connections, one to server-1 and the other to server-2. +I recommend that you start two new connections, one to <code>server-1</code> and +the other to <code>server-2</code>. -Select, insert, update, delete from each table, and see if everything is working. +Select, insert, update, delete from each table, and see if everything +is working. Also try on one of the connections: @@ -298,7 +307,8 @@ see equal values. <pre><code>INSERT INTO test_ainc VALUES (null), (null), (null); </code></pre> -Do this on both connections and see how the AUTO_INCREMENT columns just work. +Do this on both connections and see how the <code>AUTO_INCREMENT</code> columns +just work. <h1 id="finalnotes">Final Notes</h1> how-to.html @@ -62,8 +62,9 @@ The following changes where done: * `port` and `socket` settings: updated to be different for each server. -For any mysql command to use a specific server, you just need to -add a `--defaults-file=$HOWTO_DIR/etc/server-1.cnf`. +For any MySQL command to use a specific server, you just need to +add a `--defaults-file=$HOWTO_DIR/etc/server-1.cnf` (replace 1 with 2 to work +on the second server). Start two servers @@ -93,7 +94,7 @@ connecting to each one: *Please note* that this procedure did not set a `root` account password. This means that anybody can connect as `root` to your database. -For production environments it is *strongly recommended* that you change +For production environments it is **strongly recommended** that you change the `root` password, and delete the anonymous accounts. For our tests purposes, we will not do that. @@ -102,11 +103,11 @@ For our tests purposes, we will not do that. Create sample db with data on server1 ------------------------------------- -On server-1, connect as root, and create the user used by the slave: +On `server-1`, connect as root, and create the user used by the slave: mysql --defaults-file=$HOWTO_DIR/etc/server-1.cnf -u root < $HOWTO_DIR/sql/repl_user.sql -We will also create the test database, and load our test schema: +We will also create the `tigasedb` database, and load our test schema: mysqladmin --defaults-file=$HOWTO_DIR/etc/server-1.cnf -u root create tigasedb mysql --defaults-file=$HOWTO_DIR/etc/server-1.cnf -u root tigasedb < $HOWTO_DIR/sql/tigase-mysql-schema.sql @@ -123,12 +124,12 @@ Server 1 as Master We need to obtain the current master replication position, create a stable snapshot of the data. -Connect as root: +Connect as `root`: mysql --defaults-file=$HOWTO_DIR/etc/server-1.cnf -u root tigasedb This connection must be left open for the rest of this procedure. This -is required to leave the LOCK in place. +is required to leave the `LOCK` in place. Execute the following statements: @@ -152,8 +153,8 @@ Now create a dump of the data in the master: --lock-all-tables \ tigasedb > tigasedb_dump.sql -Now we need to setup the slave. First, create the tigasedb database and -load the dump taken on the master: +Now we need to setup the slave. First, create the `tigasedb` database and +load the SQL dump from the master: mysqladmin --defaults-file=$HOWTO_DIR/etc/server-2.cnf -u root create tigasedb mysql --defaults-file=$HOWTO_DIR/etc/server-2.cnf -u root tigasedb < tigasedb_dump.sql @@ -161,7 +162,7 @@ load the dump taken on the master: You should have the same data on both servers now. To finish the setup, you need to set the other master parameters on the -slave. Connect as root: +slave. Connect as `root`: mysql --defaults-file=$HOWTO_DIR/etc/server-2.cnf -u root @@ -176,21 +177,22 @@ And setup the master link: MASTER_LOG_POS=4514; START SLAVE; -You can now end the server 1 session where the LOCK was created. +You can now end the server-1 session where the `LOCK` was created. -You should have a proper master/slave relation working between server-1 -and server-2. +You should have a proper master/slave relation working between `server-1` +and `server-2`. -If you look at `SHOW MASTER STATUS` on server-1 and compare to +If you look at `SHOW MASTER STATUS` on `server-1` and compare to `SHOW SLAVE STATUS\G` (use `\G` query terminator for a more useful layout) -on server-2, you should see the same `File` and `Position` on server-1 -as `Master_Log_File` and `Read_Master_Log_Pos` on server-2. +on `server-2`, you should see the same `File` and `Position` on `server-1` +as `Master_Log_File` and `Read_Master_Log_Pos` on `server-2`. To test, insert a new row in the `tig_user` table. INSERT INTO tig_users (uid, user_id) VALUES (3, 'user3'); -If you SELECT * FROM tig_users on server-2, you should see the `user3`. +If you `SELECT * FROM tig_users` on `server-2`, you should see the +`user3` row. You can also re-check the `SHOW MASTER STATUS`/`SHOW SLAVE STATUS` and compare the `File`/`Position`. @@ -199,13 +201,13 @@ compare the `File`/`Position`. Server 2 as Master ================== -The last step is to set server 2 as master of server 1. +The last step is to set `server-2` as master of `server-1`. -Before we procede, some cautions --------------------------------- +Before we procede, some notes +----------------------------- -A master/master setup requires some configuration to make `AUTO_INCREMENT` +A master/master setup requires some configurations to make `AUTO_INCREMENT` work correctly. Our config files already include the proper `auto_increment_increment` and @@ -218,18 +220,18 @@ You should read: It boils down to this: - * `auto_increment_increment` should be equal to the number of masters you have, N; - * `auto_increment_offset` should be different, from 1 to N, on each master. + * `auto_increment_increment` should be equal to the number of masters you have, `N`; + * `auto_increment_offset` should be different, from 1 to `N`, on each master. Make server 1 slave to server 2 ------------------------------- -You need a replication user on server 2. I'll use the same one: +You need a replication user on `server-2`. We'll use the same one: mysql --defaults-file=$HOWTO_DIR/etc/server-2.cnf -u root < $HOWTO_DIR/sql/repl_user.sql -Connect to server 2, lock tables and record the master position: +Connect to `server-2`, lock tables and record the master position: mysql --defaults-file=$HOWTO_DIR/etc/server-2.cnf -u root tigasedb @@ -243,11 +245,11 @@ Connect to server 2, lock tables and record the master position: +---------------------------+----------+--------------+------------------+ 1 row in set (0.00 sec) -Then hop over to server 1, and connect as root: +Then hop over to `server-1`, and connect as `root`: mysql --defaults-file=$HOWTO_DIR/etc/server-1.cnf -u root tigasedb -Make server 1 a slave with the proper master position: +Make `server-1` a slave with the proper master position: CHANGE MASTER TO MASTER_HOST='127.0.0.1', @@ -258,26 +260,29 @@ Make server 1 a slave with the proper master position: MASTER_LOG_POS=482; START SLAVE; -Release the lock on server 2. The easiest way is just quiting the mysql shell. +Release the lock on `server-2`. The easiest way is just quiting the +`mysql` shell. -You should have a proper master/master relation working between server-1 -and server-2. +You should have a proper master/master relation working between `server-1` +and `server-2`. -If you look at `SHOW MASTER STATUS` on server-2 and compare to +If you look at `SHOW MASTER STATUS` on `server-2` and compare to `SHOW SLAVE STATUS\G` (use `\G` query terminator for a more useful layout) -on server-1, you should see the same `File` and `Position` on server-2 -as `Master_Log_File` and `Read_Master_Log_Pos` on server-1. +on `server-1`, you should see the same `File` and `Position` on `server-2` +as `Master_Log_File` and `Read_Master_Log_Pos` on `server-1`. -Do the same procedure inverting server-1 and server-2. You should also -see equal values. +Do the same procedure again, but switch `server-1` with `server-2`. You +should also see equal values. Final tests ----------- -I recommend that you start two new connections, one to server-1 and the other to server-2. +I recommend that you start two new connections, one to `server-1` and +the other to `server-2`. -Select, insert, update, delete from each table, and see if everything is working. +Select, insert, update, delete from each table, and see if everything +is working. Also try on one of the connections: @@ -287,7 +292,8 @@ And then insert rows with: INSERT INTO test_ainc VALUES (null), (null), (null); -Do this on both connections and see how the AUTO_INCREMENT columns just work. +Do this on both connections and see how the `AUTO_INCREMENT` columns +just work. Final Notes how-to.markdown edf3cb9565b598ecc480120449dfe6f40a28a600 Pedro Melo melo@simplicidade.org http://github.com/melo/mysql-master-master-how-to/commit/f9a717bbebc74c54a652db925e7cf3e49bc15656 f9a717bbebc74c54a652db925e7cf3e49bc15656

2008-06-27T04:07:20-07:00

Tweaks all over, minor ajustments of typography Updated HTML copy. Signed-off-by: Pedro Melo <melo@simplicidade.org> b0a71bb0495a1c73c3448339dda8418353d44cd2 Pedro Melo melo@simplicidade.org