设为首页 收藏本站
查看: 721|回复: 0

[经验分享] How To Set Up A Load-Balanced MySQL Cluster

[复制链接]

尚未签到

发表于 2016-10-20 08:21:32 | 显示全部楼层 |阅读模式
4 Test The MySQL Cluster
  Our MySQL cluster configuration is already finished, now it's time to test it. On the cluster management server (loadb1.example.com), run the cluster management client ndb_mgm to check if the cluster nodes are connected:
  loadb1.example.com:
ndb_mgm
  You should see this:


-- NDB Cluster -- Management Client --
ndb_mgm>
  Now type show; at the command prompt:
show;
  The output should be like this:


ndb_mgm> show;
Connected to Management Server at: localhost:1186
Cluster Configuration
---------------------
[ndbd(NDB)] 2 node(s)
id=2 @192.168.0.101 (Version: 5.0.19, Nodegroup: 0, Master)
id=3 @192.168.0.102 (Version: 5.0.19, Nodegroup: 0)

[ndb_mgmd(MGM)] 1 node(s)
id=1 @192.168.0.103 (Version: 5.0.19)

[mysqld(API)] 2 node(s)
id=4 @192.168.0.101 (Version: 5.0.19)
id=5 @192.168.0.102 (Version: 5.0.19)

ndb_mgm>
  If you see that your nodes are connected, then everything's ok!
  Type
quit;
  to leave the ndb_mgm client console.
  Now we create a test database with a test table and some data on sql1.example.com:
  sql1.example.com:
mysql -u root -p
CREATE DATABASE mysqlclustertest;
USE mysqlclustertest;
CREATE TABLE testtable (i INT) ENGINE=NDBCLUSTER;
INSERT INTO testtable () VALUES (1);
SELECT * FROM testtable;
quit;
  (Have a look at the CREATE statment: We must use ENGINE=NDBCLUSTER for all database tables that we want to get clustered! If you use another engine, then clustering will not work!)
  The result of the SELECT statement should be:


mysql> SELECT * FROM testtable;
+------+
| i    |
+------+
| 1    |
+------+
1 row in set (0.03 sec)
  Now we create the same database on sql2.example.com (yes, we still have to create it, but afterwards testtable and its data should be replicated to sql2.example.com because testtable uses ENGINE=NDBCLUSTER):
  sql2.example.com:
mysql -u root -p
CREATE DATABASE mysqlclustertest;
USE mysqlclustertest;
SELECT * FROM testtable;
  The SELECT statement should deliver you the same result as before on sql1.example.com:


mysql> SELECT * FROM testtable;
+------+
| i    |
+------+
| 1    |
+------+
1 row in set (0.04 sec)
  So the data was replicated from sql1.example.com to sql2.example.com. Now we insert another row into testtable:
  sql2.example.com:
INSERT INTO testtable () VALUES (2);
quit;
  Now let's go back to sql1.example.com and check if we see the new row there:
  sql1.example.com:
mysql -u root -p
USE mysqlclustertest;
SELECT * FROM testtable;
quit;
  You should see something like this:


mysql> SELECT * FROM testtable;
+------+
| i    |
+------+
| 1    |
| 2    |
+------+
2 rows in set (0.05 sec)
  So both MySQL cluster nodes alwas have the same data!
  Now let's see what happens if we stop node 1 (sql1.example.com): Run
  sql1.example.com:
killall ndbd
  and check with
ps aux | grep ndbd | grep -iv grep
  that all ndbd processes have terminated. If you still see ndbd processes, run another
killall ndbd
  until all ndbd processes are gone.
  Now let's check the cluster status on our management server (loadb1.example.com):
  loadb1.example.com:
ndb_mgm
  On the ndb_mgm console, issue
show;
  and you should see this:


ndb_mgm> show;
Connected to Management Server at: localhost:1186
Cluster Configuration
---------------------
[ndbd(NDB)] 2 node(s)
id=2 (not connected, accepting connect from 192.168.0.101)
id=3 @192.168.0.102 (Version: 5.0.19, Nodegroup: 0, Master)

[ndb_mgmd(MGM)] 1 node(s)
id=1 @192.168.0.103 (Version: 5.0.19)

[mysqld(API)] 2 node(s)
id=4 @192.168.0.101 (Version: 5.0.19)
id=5 @192.168.0.102 (Version: 5.0.19)

ndb_mgm>
  You see, sql1.example.com is not connected anymore.
  Type
quit;
  to leave the ndb_mgm console.
  Let's check sql2.example.com:
  sql2.example.com:
mysql -u root -p
USE mysqlclustertest;
SELECT * FROM testtable;
quit;
  The result of the SELECT query should still be


mysql> SELECT * FROM testtable;
+------+
| i    |
+------+
| 1    |
| 2    |
+------+
2 rows in set (0.17 sec)
  Ok, all tests went fine, so let's start our sql1.example.com node again:
  sql1.example.com:
ndbd

运维网声明 1、欢迎大家加入本站运维交流群:群②:261659950 群⑤:202807635 群⑦870801961 群⑧679858003
2、本站所有主题由该帖子作者发表,该帖子作者与运维网享有帖子相关版权
3、所有作品的著作权均归原作者享有,请您和我们一样尊重他人的著作权等合法权益。如果您对作品感到满意,请购买正版
4、禁止制作、复制、发布和传播具有反动、淫秽、色情、暴力、凶杀等内容的信息,一经发现立即删除。若您因此触犯法律,一切后果自负,我们对此不承担任何责任
5、所有资源均系网友上传或者通过网络收集,我们仅提供一个展示、介绍、观摩学习的平台,我们不对其内容的准确性、可靠性、正当性、安全性、合法性等负责,亦不承担任何法律责任
6、所有作品仅供您个人学习、研究或欣赏,不得用于商业或者其他用途,否则,一切后果均由您自己承担,我们对此不承担任何法律责任
7、如涉及侵犯版权等问题,请您及时通知我们,我们将立即采取措施予以解决
8、联系人Email:admin@iyunv.com 网址:www.yunweiku.com

所有资源均系网友上传或者通过网络收集,我们仅提供一个展示、介绍、观摩学习的平台,我们不对其承担任何法律责任,如涉及侵犯版权等问题,请您及时通知我们,我们将立即处理,联系人Email:kefu@iyunv.com,QQ:1061981298 本贴地址:https://www.yunweiku.com/thread-288625-1-1.html 上篇帖子: [原创]MySQL中MyISAM引擎和Heap引擎执行速度性能测试 下篇帖子: MySQL中MyISAM引擎和Heap引擎执行速度性能测试
您需要登录后才可以回帖 登录 | 立即注册

本版积分规则

扫码加入运维网微信交流群X

扫码加入运维网微信交流群

扫描二维码加入运维网微信交流群,最新一手资源尽在官方微信交流群!快快加入我们吧...

扫描微信二维码查看详情

客服E-mail:kefu@iyunv.com 客服QQ:1061981298


QQ群⑦:运维网交流群⑦ QQ群⑧:运维网交流群⑧ k8s群:运维网kubernetes交流群


提醒:禁止发布任何违反国家法律、法规的言论与图片等内容;本站内容均来自个人观点与网络等信息,非本站认同之观点.


本站大部分资源是网友从网上搜集分享而来,其版权均归原作者及其网站所有,我们尊重他人的合法权益,如有内容侵犯您的合法权益,请及时与我们联系进行核实删除!



合作伙伴: 青云cloud

快速回复 返回顶部 返回列表