MySQL cluster configuration

Source: Internet
Author: User

From: http://topic.csdn.net/u/20100621/16/C9436C17-374C-4C3A-B075-A18670143FD1.html

Install mysql-Cluster

System centos5.1 32-bit (how to use a 64-bit RPM package)

Http://dev.mysql.com/get/downloads/MySQL-Cluster-7.0 corresponds to the package name below

A total of five packages:

MySQL-Cluster-gpl-client-7.1.3-1.rhel5.i386.rpm

MySQL-Cluster-gpl-management-7.1.3-1.rhel5.i386.rpm

MySQL-Cluster-gpl-server-7.1.3-1.rhel5.i386.rpm

MySQL-Cluster-gpl-storage-7.1.3-1.rhel5.i386.rpm

MySQL-Cluster-gpl-tools-7.1.3-1.rhel5.i386.rpm

 

Three centos servers:

Management node (ndb_mgmd): 192.168.1.14

 

SQL Node 1 (mysqld): 192.168.1.15

SQL Node 1 (mysqld): 192.168.1.11

 

Data Node (ndbd): 192.168.1.15

Data Node (ndbd): 192.168.1.11

 

// -------------------------------------------------------------------- Start with this (this is used for all the seven hosts)

The first thing to do is to turn off the firewalls of the seven hosts (if not, every node cannot connect)

 

Disable Firewall:

Service iptables stop;

Flushing firewall rules: [OK]

Setting chains to policy accept: Filter [OK]

Unloading iptables modules: [OK]

How can I close it like this;

 

Create a folder:

Storage node: mkdir/var/lib/MySQL/Data

Management node: mkdir/var/lib/MySQL-Cluster

SQL node: yes or no

 

Grant permissions to two files:

Chmod-r 1777/var/lib/MySQL

Chmod-r 1777/var/lib/MySQL-Cluster

// -------------------------------------------------------------------- End with this

 

Management node installation:

MySQL-Cluster-gpl-management-7.0.9-0.rhel4.x86_64.rpm;

MySQL-Cluster-gpl-tools-7.0.9-0.rhel4.x86_64.rpm;

Rpm-IVH MySQL-Cluster-gpl-management-7.0.9-0.rhel4.x86_64.rpm

Rpm-IVH MySQL-Cluster-gpl-tools-7.0.9-0.rhel4.x86_64.rpm

 

VI/var/lib/MySQL-cluster/config. ini

 

[Ndbd default]

Noofreplicas = 2

Datamemory = 80 m

Indexmemory = 18 m

[TCP default]

Sendbuffermemory = 2 m

Receivebuffermemory = 2 m

[Ndb_mgmd default]

Portnumber = 1186

Datadir =/var/lib/MySQL-Cluster

[Ndb_mgmd]

Id = 1

Hostname = 192.168.1.14

[Ndbd]

Id = 2

Hostname = 192.168.1.15

Datadir =/var/lib/MySQL/Data

[Ndbd]

Id = 3

Hostname = 192.168.1.11

Datadir =/var/lib/MySQL/Data

[Mysqld]

Id = 14

Hostname = 192.168.1.15

[Mysqld]

Id = 15

Hostname = 192.168.1.11

[Mysqld]

Id = 16

 

// Start the management Node
Ndb_mgmd-F/var/lib/MySQL-cluster/config. ini

/******************** The above is the Installation Management node ************* *************/

 

 

Storage node Installation

MySQL-Cluster-gpl-storage-7.0.9-0.rhel4.x86_64.rpm

Rpm-IVH MySQL-Cluster-gpl-storage-7.0.9-0.rhel4.x86_64.rpm

VI/etc/My. CNF // confirm that the following modified
[Mysqld]
Max_connections = 100
Slow_query_log =/var/lib/MySQL-cluster/slow_query.log
Long_query_time = 1
Datadir =/var/lib/MySQL-Cluster
Ndbcluster
NDB-connectstring = 192.168.1.14

[Mysql_cluster]
NDB-connectstring = 192.168.1.14

 

Initialize the database that starts the data node,
Note: // ndbd-initial cannot be executed on all data nodes at the same time. Otherwise, all data is deleted. That is, this command can only be executed on one of the data nodes.
Ndbd-initial

 

How:

[Ndbd] info -- configuration fetched from '10. 50.8.8: 1186 ', generation: 1

 

SQL node installation:

MySQL-Cluster-gpl-client-7.0.9-0.rhel4.x86_64.rpm

MySQL-Cluster-gpl-server-7.0.9-0.rhel4.x86_64.rpm

 

Rpm-IVH MySQL-Cluster-gpl-server-7.0.9-0.rhel4.x86_64.rpm

Rpm-IVH MySQL-Cluster-gpl-client-7.0.9-0.rhel4.x86_64.rpm -- nodeps-force Red must be written or not installed.

VI/etc/My. CNF // confirm that the following modified
[Mysqld]

Ndbcluster

NDB-connectstring = 192.168.1.14: 1186

[Mysql_cluster]

NDB-connectstring = 192.168.1.14: 1186

 

I used this mysqld_safe to start the SQL node & no error

After execution

100308 13:46:32 mysqld_safe logging to '/var/lib/MySQL/localhost. localdomain. err '.

100308 13:46:32 mysqld_safe starting mysqld daemon with databases from/var/lib/MySQL

The SQL node is successful.

 

Under the host of the Management node (192.168.1.14)

Ndb_mgm

 

Ndb_mgm> show

Connected to management server at: localhost: 1186
Cluster configuration
---------------------
[Ndbd (NDB)] 2 node (s)
Id = 2 @ 192.168.1.15 (mysql-5.1.44 ndb-7.1.3, node group: 0, Master)
Id = 3 @ 192.168.1.11 (mysql-5.1.44, nodegroup: 0)

[Ndb_mgmd (MGM)] 1 node (s)
Id = 1 @ 192.168.1.14 (mysql-5.1.44 ndb-7.1.3)

[Mysqld (API)] 3 node (s)
Id = 14 @ 192.168.1.15 (mysql-5.1.44 ndb-7.1.3)
Id = 15 @ 192.168.1.11 (mysql-5.1.44 ndb-7.1.3)
Id = 16 (not connected, accepting connect from any host)

 

The above information is displayed successfully.

If not connected appears, accepting connect from any host is not enabled for the SQL node.

When the mysql-5.1.39 ndb-7.0.9 appears, staring nodegroup: 0 indicates that the storage node is not started. If your configuration is correct (that is, your firewall is irrelevant)

 

******************/

Dynamic Update Node

Close management node my management node here is 1

Ndb_mgm> 1 stop

Exit ndb_mgm

Shell> VI/var/lib/MySQL-cluster/config. ini

If we add an ndbd Node

[Ndbd]

Id = 6

Hostname = 10.50.8.13

Datadir =/var/lib/MySQL/Data

Save and exit

Ndb_mgmb-F config. ini-Reload

 

13:47:15 [mgmtsrvr] info -- NDB cluster management server. mysql-5.1.39 ndb-7.0.9b

13:47:16 [mgmtsrvr] info -- Reading cluster configuration from 'config. ini'

It starts successfully.

Restart each node.

The NDB node executes ndb_mgm> 2 restart on the Management node (you should know how to install it in ndb_mgm)

The SQL node executes service myql stop mysqld_save on the SQL node;

Show the results on the Management node.

 

1. Management node startup: ndb_mgmd-F/var/lib/MySQL-cluster/config. ini ndb_mgmd-F config. ini-Reload

2. Data Node start: ndbd start ndb_mgm> 2 restart data node restart
3. SQL node startup: mysqld_safe & off: Service MySQL stop mysqld_save

Related Article

Contact Us

The content source of this page is from Internet, which doesn't represent Alibaba Cloud's opinion; products and services mentioned on that page don't have any relationship with Alibaba Cloud. If the content of the page makes you feel confusing, please write us an email, we will handle the problem within 5 days after receiving your email.

If you find any instances of plagiarism from the community, please send an email to: info-contact@alibabacloud.com and provide relevant evidence. A staff member will contact you within 5 working days.

A Free Trial That Lets You Build Big!

Start building with 50+ products and up to 12 months usage for Elastic Compute Service

  • Sales Support

    1 on 1 presale consultation

  • After-Sales Support

    24/7 Technical Support 6 Free Tickets per Quarter Faster Response

  • Alibaba Cloud offers highly flexible support services tailored to meet your exact needs.