How to install MYSQL NDB cluster - Revision history

Admin: /* Conclusion */

2021-07-13T03:46:15Z

Conclusion

2021-07-13T01:20:36Z

Management node

2019-09-03T01:23:09Z

Testing

2019-04-07T21:14:01Z

Management node

2019-04-07T21:12:59Z

Data node

2019-04-07T16:48:35Z

Data node

2019-04-07T06:35:25Z

Management node

2019-02-14T01:23:56Z

Troubleshooting

2019-01-24T04:46:16Z

How to add a new SQL or data node

2018-11-02T20:55:52Z

Troubleshooting

← Older revision		Revision as of 03:46, 13 July 2021
Line 855:		Line 855:

	=Conclusion=		=Conclusion=
−	We have ~~convert~~ a whole working environment that you can put in production in this tutorial by setting up a NDB cluster with 5 nodes, 2 load balancing and 1 application node. Hope this tutorial was helpful.	+	We have discus about a whole working environment that you can put in production in this tutorial by setting up a NDB cluster with 5 nodes, 2 load balancing and 1 application node. Hope this tutorial was helpful.

@@ Line 97: / Line 97: @@
   cd mysql-cluster-gpl-7.6.7-linux-glibc2.12-x86_64
   cd bin
-  sudo cp ndb_mgm /usr/bin/
+  sudo cp ndb_mgm /usr/local/bin/
-  sudo cp ndb_mgmd /usr/bin/
+  sudo cp ndb_mgmd /usr/local/bin/
   cd /usr/bin/
   sudo chmod 755 ndb_mg*
@@ Line 145: / Line 145: @@
 Set back and relax
-AFter the scrpt complete type command
+After the script complete type command
   ndb_mgm

@@ Line 798: / Line 798: @@
 ==Testing==
 * First test
-Add and new user. If it works with no problem, move the the next test.
+Add new user. If it works with no problem, move to the next test.
 * Second test
-Stop mysql on db2004 or db2009 and try to ready or write by creating or reading from the application
+Stop mysql on db2004 or db2009 and try to read or write by creating or reading from the application
 * Third test
-while one of the mysql node is stopped, stop one of the data node too and try to ready and write from the application
+while one of the mysql node is stopped, stop one of the data node too and try to read and write from the application
 * Fourth test
 stop heartbeat on haproxy2001 and try to read or write from the application.

@@ Line 168: / Line 168: @@
   id=5 (not connected, accepting connect from db2009.dfw.ppnet)
 We can see that the management node is up and running and the data nodes and SQL nodes are stay down. In the next session we are going to setup the data nodes
 ==Data node==

@@ Line 210: / Line 210: @@
   #start the service
   cd
-  ndbd
+  sudo ndbd
 save the file and close it. Make the file executable
   sudo chmod +x data._node.sh

@@ Line 174: / Line 174: @@
   #!/bin/bash
   #create a folder called files under /tmp/
   echo " Creating folder"

@@ Line 128: / Line 128: @@
       fi
   #Start the manegement node
-  echo"starting the manegement node"
+  echo "starting the manegement node"
   sleep 3
   cd

← Older revision		Revision as of 01:23, 14 February 2019
Line 834:		Line 834:

	sudo systemctl start mysql		sudo systemctl start mysql
		+
		+	=Maintenance=
		+	to shutdown the whole cluster, login to the management node (db2008) at the shell type in
		+	ppaul@db2008:~$ ndb_mgm -e shutdown
		+	output
		+	Connected to Management Server at: localhost:1186
		+	3 NDB Cluster node(s) have shutdown.
		+	Disconnecting to allow management server to shutdown.

	=References=		=References=

@@ Line 498: / Line 498: @@
 ==How to add a new SQL or data node==
 *Step 1
-Before you add a new SQL or data node, make sure if you have using the IP address that the management node can ping the new node and the new node can ping also the management node. If you are using the FQDN or hostanme, make sure that name can be resolved by both the management node and the new node.
+Before you add a new SQL or data node, make sure if you are using an IP  that the management node can ping the new node and the new node can ping also the management node. If you are using the FQDN or hostanme, make sure that name can be resolved by both the management node and the new node.
 *step 2
 Login to your management node and stop the management node with the command "1 stop" 1 being the node ID

@@ Line 826: / Line 826: @@
   [ERROR] NDB: error (1) Configuration error: Error: Could not alloc node id at db2008.dfw.ppnet port 1186: Connection done from wrong host ip 10.192.16.29.
 Here db2008.dfw.ppnet is the management node and 10.192.16.29 is the management node IP address.
 =References=