MySQL Cluster Tutorial - cdn.oreillystatic.com

More documents

Recommendations

Info

Luckily, the solution is rather simple. Just configure another SQL Node to do binary logging. Setting up Replication between Clusters Setting up Geographical Replication between two Cluster is as simple as setting it up between two ‘normal’ MySQL servers. We’ll need to start a second Cluster for this. shell> ndb_mgmd --initial -f /opt/mysqlcluster/config_Slave.ini --configdir=/ opt/mysqlcluster/ndb_Slave shell> ndbd -c localhost:1187 shell> mysqld_safe --defaults-file=/opt/mysqlcluster/my_Slave.cnf & To access the Slave MySQL Cluster using the ndb_mgm and mysql tool, use the following: shell> ndb_mgm -c localhost:1187 shell> mysql -S /tmp/mysql_Slave On the Master Cluster you create a MySQL user which has the REPLICATION USER privilege. You have to do this on every SQL Node which you are doing binary logging: shell> mysql mysql_A> GRANT REPLICATION SLAVE ON *.* TO repl@127.0.0.1; shell> mysql -S /tmp/mysql_B mysql_B> GRANT REPLICATION SLAVE ON *.* TO repl@127.0.0.1; The reason you need to do it on both is because the grant tables in MySQL are local to each node. They are MyISAM and are not part of Cluster. Now we need to the binary log position from which we are going to start the replication. We will use the SQL Node A to start with. Copyright © 2010, Oracle and/or its affiliates. All rights reserved. 76/81
shell> mysql mysql_A:(none)> SHOW MASTER STATUS; +------------------------+----------+-.. | File | Position | .. +------------------------+----------+-.. | master_A_binlog.000012 | 214 | .. +------------------------+----------+-.. Using this information we can go to the Slave and issue the CHANGE MASTER command. mysql_Slave> CHANGE MASTER TO MASTER_HOST='127.0.0.1',MASTER_PORT=3306, MASTER_USER='repl', MASTER_LOG_FILE='master_A_binlog.000012', MASTER_LOG_POS=214; Then start the slave, and use SHOW SLAVE STATUS to see if it is working: mysql_Slave> START SLAVE; mysql_Slave> SHOW SLAVE STATUS\G .. Slave_IO_State: Waiting for master to send event .. Slave_IO_Running: Yes Slave_SQL_Running: Yes .. Master_Server_Id: 1 You create the table on the Master side, using the NDBCluster engine. It should get created on the Slave as well: mysql_A> CREATE TABLE attendees ( id INT UNSIGNED NOT NULL AUTO_INCREMENT, email VARCHAR(200), PRIMARY KEY (id) ) ENGINE=NDBCluster; Now you can simply insert data and see it replicating. Handling LOST_EVENTS Lets see what happens when we shutdown the mysql_A server and start again. shell> mysqladmin -S /tmp/mysql shutdown shell> mysqld_safe --defaults-file=/opt/mysqlcluster/my_A.cnf & Now, check the Slave: shell> mysql -S /tmp/mysql_Slave mysql_Slave> SHOW SLAVE STATUS\G .. Last_Errno: 1590 Last_Error: The incident LOST_EVENTS occured on the master. Message: mysqld startup .. It is now up to you do decide whether you can continue skipping the error, knowing that you might have lost data or switch to the other replication channel. Skipping can be done doing this: Copyright © 2010, Oracle and/or its affiliates. All rights reserved. 77/81
Page 1 and 2:
MySQL Cluster Tutorial O’Reilly M
Page 3 and 4:
ndbinfo Data Node Statistics! 39 nd
Page 5 and 6:
Introduction MySQL Cluster is a too
Page 7 and 8:
MySQL Cluster in short • MySQL Cl
Page 9 and 10:
Installation and Configuration In t
Page 11 and 12:
Configuration my_Slave.cnf Configur
Page 13 and 14:
Starting & Using MySQL Cluster Star
Page 15 and 16:
ndb_mgm> show Connected to Manageme
Page 17 and 18:
Administer MySQL Cluster MySQL Clus
Page 19 and 20:
ndb_mgm> 2 restart Node 2: Node shu
Page 21 and 22:
to load problems such as timing iss
Page 23 and 24:
MySQL Cluster Manager MySQL Cluster
Page 25 and 26: • The management node(s) can cont
Page 27 and 28: Example configuration Throughout th
Page 29 and 30: example, the MySQL Cluster installa
Page 31 and 32: 3. Fetch the port parameter to conn
Page 33 and 34: Introducing MySQL Cluster Manager t
Page 35 and 36: within 4 heartbeat intervals. This
Page 37 and 38: • Stored routines and other none
Page 39 and 40: NDB Info ndbinfo Data Node Statisti
Page 41 and 42: For the redo log space, there is 1
Page 43 and 44: NDB API NDB API Overview The NDB AP
Page 45 and 46: static void run_application(MYSQL &
Page 47 and 48: const NdbDictionary::Index *myPInde
Page 49 and 50: MySQL Cluster Connector for Java Te
Page 51 and 52: • SessionFactory: There is one in
Page 53 and 54: Figure 4: Performance of OpenJPA Ad
Page 55 and 56: config.ini: [ndbd default]noofrepli
Page 57 and 58: The next step is to write the appli
Page 59 and 60: mysql> select * from clusterdb.empl
Page 61 and 62: Compiling and running the ClusterJ
Page 63 and 64: Employee.java: import javax.persist
Page 65 and 66: Main.java (part 2): userTransaction
Page 67 and 68: Main.java (part 4): em.close(); ent
Page 69 and 70: This fails with an error saying the
Page 71 and 72: Scaling and Performance MySQL Nodes
Page 73 and 74: Geographical Replication The MySQL
Page 75: You can, however, have a more reada
Page 79 and 80: On the Slave we now issue the CHANG
Page 81: Security It should be noted right f
show all

MySQL Cluster Tutorial - cdn.oreillystatic.com

You also want an ePaper? Increase the reach of your titles

Delete template?

Save as template?