MariaDB社区

 找回密码
 注册

QQ登录

只需一步,快速开始

搜索
查看: 4022|回复: 6
打印 上一主题 下一主题

有人在solaris上测试cluster成功过吗?

[复制链接]
跳转到指定楼层
1#
发表于 2010-2-25 09:04:41 | 只看该作者 回帖奖励 |正序浏览 |阅读模式
我的SQL 节点无法加入cluster中!!!有人遇到这个问题吗?

我参考这个white paper [
Installation of MySQLTM 5.1 Cluster Software on the SolarisTM 10 OS for x64 Platforms
] 安装 mysql cluster于 solaris10.

Management node, DATA node, SQL node 都可以启动成功,但是下面的命令显示, SQL nodes没有加入cluser中。
"ndb_mgm> show


下面是我在mysql论坛的提问,结果没有任何人回答。请朋友们帮助我!!!万分感激!!!折磨我好多天了!!!

I have tried to run Management node, DATA node and SQL node on the same server, please refer to Part I.
I tried run DATA node on one server, and MANAGEMENT node, SQL node on the other server, please refer to Part II.
But none of this two cases works!
------------------------------------------------------------------------
------------------------------------------------------------------------
------------------------------------------------------------------------
Part I: Single server

Management node, data node and SQL node all run on the same server.
They share the same my.cnf
-------------------------------------

My environment:
1)server: sunws05, Solaris 10 SPARC
2)software: mysql-cluster-gpl-7.0.9-solaris10-sparc-64bit.pkg [unzipped]

------------------------------------------------------------------------
steps:
1. Log in the server and switch to root context:
login as: yxiang
...
sunws05:/home/yxiang$
sunws05:/home/yxiang$ su
Password:***
# su - root
Sun Microsystems Inc.   SunOS 5.10      Generic January 2005
sunws05:/#
sunws05:/# bash

-------------------------------------

2. clean all mysql related things:

2.1 After all mysql-related processes are killed:
sunws05:/# ps -ef |grep mysql
    root 23297 22979   0 09:08:39 pts/3       0:00 grep mysql
sunws05:/#

2.2 uninstall mysql
sunws05:/# pkginfo | grep mysql
application mysql                            MySQL Cluster Server (GPL)
sunws05:/# pkgrm mysql
    .........................
    Removal of <mysql> was successful.

2.3 clean all data and dirs:
sunws05:/# cd /opt/mysql/mysql
sunws05:/opt/mysql/mysql# ls
data           mysql-cluster
sunws05:/opt/mysql/mysql# rm -r data
sunws05:/opt/mysql/mysql# rm -r mysql-cluster
sunws05:/opt/mysql/mysql#

sunws05:/# cd /var/lib
sunws05:/var/lib# ls
gdm            log            mysql          mysql-cluster  pgsql          sgml
sunws05:/var/lib# rm -r mysql
sunws05:/var/lib#

sunws05:/var/lib# cd /etc/mysql
sunws05:/etc/mysql# ls
config.ini  my.cnf      temp
sunws05:/etc/mysql#
sunws05:/etc/mysql# rm config.ini
sunws05:/etc/mysql# rm my.cnf


-------------------------------------


3. Installation:
3.1 add mysql user and group
sunws05:/var/lib# groupadd mysql
UX: groupadd: ERROR: mysql is already in use.  Choose another.
sunws05:/var/lib# useradd -g mysql mysql
sunws05:/var/lib#

3.2 install software
sunws05:/opt/yxiang_soft# pkgadd -d mysql-cluster-gpl-7.0.9-solaris10-sparc-64bit.pkg
...
MySQL Cluster Server (GPL)(sun4u) 7.0.9
Copyright 2000-2008 MySQL AB, 2008 Sun Microsystems, Inc.  All rights reserved.
Use is subject to license terms.
Using </opt/mysql> as the package base directory.
...
Do you want to continue with the installation of <mysql> [y,n,?]
...
## Installing part 1 of 1.
...
/opt/mysql/mysql/bin/mysql
...
/opt/mysql/mysql/bin/mysql_upgrade
...
/opt/mysql/mysql/bin/mysqladmin
/opt/mysql/mysql/bin/mysqlbinlog
...
Installation of <mysql> was successful.


-------------------------------------


4.review mysql cluster info:
4.1 mysql cluster
sunws05:/# cd /opt/mysql/mysql
sunws05:/opt/mysql/mysql# ls
COPYING            README             docs               man                share
EXCEPTIONS-CLIENT  bin                include            mysql-test         sql-bench
INSTALL-BINARY     data               lib                scripts            support-files
sunws05:/opt/mysql/mysql# cd data
sunws05:/opt/mysql/mysql/data# ls
mysql  test
~~~~~~~~~~~Here we can see that two default sub-databases are installed.

4.2 priority of mysql
sunws05:/opt/mysql# ls -l mysql
total 218
-rw-r--r--   1 root     bin        19071 Nov 18 06:01 COPYING
-rw-r--r--   1 root     bin         5139 Nov 18 06:01 EXCEPTIONS-CLIENT
-rw-r--r--   1 root     bin         9439 Nov 18 06:01 INSTALL-BINARY
-rw-r--r--   1 root     bin        62989 Nov 18 06:01 README
drwxr-xr-x   2 root     bin         2048 Feb 12 09:42 bin
drwxr-xr-x   4 mysql    mysql        512 Feb 12 09:42 data
drwxr-xr-x   2 root     bin          512 Feb 12 09:42 docs
drwxr-xr-x   3 root     bin         1024 Feb 12 09:42 include
drwxr-xr-x   3 root     bin         1024 Feb 12 09:42 lib
drwxr-xr-x   4 root     bin          512 Feb 12 09:42 man
drwxr-xr-x  10 mysql    mysql        512 Feb 12 09:43 mysql-test
drwxr-xr-x   2 root     bin          512 Feb 12 09:43 scripts
drwxr-xr-x  28 root     bin         1024 Feb 12 09:43 share
drwxr-xr-x   5 root     bin         1024 Feb 12 09:43 sql-bench
drwxr-xr-x   2 root     bin          512 Feb 12 09:43 support-files
sunws05:/opt/mysql#


-------------------------------------


5. Configure mysql cluster
Management node, data node and SQL node all run on the same server.
They share the same my.cnf

5.1 /etc/mysql/my.cnf
###################[my.cnf for Management/SQL/storage node]####################
[mysqld]
user=mysql
ndbcluster
ndb-connectstring=10.80.1.15
datadir=/var/lib/mysql
[ndb_mgm]
connect-string=10.80.1.15
[ndb_mgmd]
config-file=/etc/mysql/config.ini
#below section is for storage node.
[mysql_cluster]
ndb-connectstring=10.80.1.15

5.2 /etc/mysql/config.ini
###################[config.ini for management node]####################
[ndbd default]
NoOfReplicas=2
DataMemory=200M
IndexMemory=200M
DataDir=/export/mysql/mysql-cluster
[ndb_mgmd default]
DataDir=/export/mysql/mysql-cluster
[ndb_mgmd]
Id=1
HostName=10.80.1.15
[ndbd]
Id=2
HostName=10.80.1.15
[ndbd]
Id=3
HostName=10.80.1.16
[mysqld]
HostName=10.80.1.15
[mysqld]
分享到:  QQ好友和群QQ好友和群 QQ空间QQ空间 腾讯微博腾讯微博 腾讯朋友腾讯朋友
收藏收藏 转播转播 分享分享 分享淘帖 顶 踩
6#
发表于 2010-3-4 13:55:27 | 只看该作者
没有细看,有的只是提示:
1、所以的安装都用rpm包方式的,最好是用官方发布的最新的,适合你OS环境的。
2、你的问题与配置有关,仔细检查你的配置文件。如:server-id等。
3、OS方面的配置文件也要检查,如hosts
另外建议你看看"深入浅出MySQL数据库开发、优化与管理维护.pdf"一书中关于cluster一章节,简单易学。我放在了文档资料栏目中了,你找找吧...
5#
 楼主| 发表于 2010-2-25 09:10:43 | 只看该作者
6.2 start data node:
sunws05:/# ndbd
2010-02-12 13:51:52 [ndbd] INFO -- Configuration fetched from '10.80.1.15:1186', generation: 1

6.2.1 show data node info:
sunws05:/# ndb_mgm
-- NDB Cluster -- Management Client --
ndb_mgm> show
Connected to Management Server at: 10.80.1.15:1186
Cluster Configuration
---------------------
[ndbd(NDB)] 2 node(s)
id=2 @10.80.1.15 (mysql-5.1.39 ndb-7.0.9, starting, Nodegroup: 0)
id=3 (not connected, accepting connect from 10.80.1.16)

[ndb_mgmd(MGM)] 1 node(s)
id=1 @10.80.1.15 (mysql-5.1.39 ndb-7.0.9)

[mysqld(API)] 2 node(s)
id=4 (not connected, accepting connect from 10.80.1.15)
id=5 (not connected, accepting connect from any host)

ndb_mgm>

6.3 start SQL node:
sunws05:/# mysqld_safe &

6.3.1 show error file:
sunws05:/var/lib/mysql/mysql# vi /var/lib/mysql/sunws05.err
"/var/lib/mysql/sunws05.err" 25 lines, 1682 characters
100212 13:53:43 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql
100212 13:53:43 [Note] Plugin 'FEDERATED' is disabled.
InnoDB: The first specified data file ./ibdata1 did not exist:
InnoDB: a new database to be created!
100212 13:53:43 InnoDB: Setting file ./ibdata1 size to 10 MB
InnoDB: Database physically writes the file full: wait...
100212 13:53:44 InnoDB: Log file ./ib_logfile0 did not exist: new to be created
InnoDB: Setting log file ./ib_logfile0 size to 5 MB
InnoDB: Database physically writes the file full: wait...
100212 13:53:44 InnoDB: Log file ./ib_logfile1 did not exist: new to be created
InnoDB: Setting log file ./ib_logfile1 size to 5 MB
InnoDB: Database physically writes the file full: wait...
InnoDB: Doublewrite buffer not found: creating new
InnoDB: Doublewrite buffer created
InnoDB: Creating foreign key constraint system tables
InnoDB: Foreign key constraint system tables created
100212 13:53:45 InnoDB: Started; log sequence number 0 0
100212 13:53:45 [Note] NDB: NodeID is 4, management server '10.80.1.15:1186'
100212 13:53:46 [Note] NDB[0]: NodeID: 4, no storage nodes connected (timed out)
100212 13:53:46 [Warning] NDB: server id set to zero will cause any other mysqld with bin log to log with wrong server id
100212 13:53:46 [Note] Starting Cluster Binlog Thread
100212 13:53:46 [Note] Event Scheduler: Loaded 0 events
100212 13:54:01 [Warning] NDB : Tables not available after 15 seconds. Consider increasing --ndb-wait-setup value
100212 13:54:01 [Note] /opt/mysql/mysql/bin/mysqld: ready for connections.
Version: '5.1.39-ndb-7.0.9-cluster-gpl' socket: '/tmp/mysql.sock' port: 3306 MySQL Cluster Server (GPL)
~~~~~~~~we can see that mysqld is stared!!! but it does NOT work, i'll show you later.

6.3.2 show cluster info:
sunws05:/# ndb_mgm
-- NDB Cluster -- Management Client --
ndb_mgm> show
Connected to Management Server at: 10.80.1.15:1186
Cluster Configuration
---------------------
[ndbd(NDB)] 2 node(s)
id=2 @10.80.1.15 (mysql-5.1.39 ndb-7.0.9, starting, Nodegroup: 0)
id=3 (not connected, accepting connect from 10.80.1.16)

[ndb_mgmd(MGM)] 1 node(s)
id=1 @10.80.1.15 (mysql-5.1.39 ndb-7.0.9)

[mysqld(API)] 2 node(s)
id=4 (not connected, accepting connect from 10.80.1.15)
id=5 (not connected, accepting connect from any host)

ndb_mgm>

~~~~~~we can see, SQL node does NOT join the mysql cluster!!!


6.3.3 Now, let's see the error file[/var/lib/mysql/sunws05.err] again, i find that below contents are added:
100212 14:00:12 [Warning] NDB: Could not acquire global schema lock (4009)Cluster Failure
100212 14:03:15 [Warning] NDB: Could not acquire global schema lock (4009)Cluster Failure
100212 14:03:53 [Warning] NDB: Could not acquire global schema lock (4009)Cluster Failure

6.3.4 create DB:
mysql> CREATE TABLE Persons(
-> Id_P int,
-> LastName varchar(255),
-> FirstName varchar(255),
-> Address varchar(255),
-> City varchar(255)
-> )ENGINE=NDBCLUSTER;
ERROR 1005 (HY000): Can't create table 'genview.Persons' (errno: 157)



You can see that SQL NODE is started, but does NOT join the cluster.
I tried similar configuraiotn on two redhat EL 5.3 servers, everything is OK, even when server-id is NOT set!!!
4#
 楼主| 发表于 2010-2-25 09:09:46 | 只看该作者
================================[two solaris 10 servers testing]================================

precondition: all processes are killed and all log files are removed.

Part II-->1: Configuration

To remove the warning[Could not acquire global schema lock (4009)Cluster Failure], i used two solaris 10 servers:

10.80.1.15 ; DATA node,
10.80.1.117; MANAGEMENT node and SQL node.


------------------------------------
#/etc/mysql/config.ini @ 10.80.1.117
[ndbd default]
NoOfReplicas=2
DataMemory=400M
IndexMemory=400M
DataDir=/export/mysql/mysql-cluster
[ndb_mgmd default]
DataDir=/export/mysql/mysql-cluster
[ndb_mgmd]
Id=1
HostName=10.80.1.117
[ndbd]
Id=2
HostName=10.80.1.15
[ndbd]
Id=3
HostName=10.80.1.16 #reserved
[mysqld]
Id=4
HostName=10.80.1.117
[mysqld]
Id=5
HostName=10.80.1.15


------------------------------------
#/etc/mysql/my.cnf @ 10.80.1.117
[mysqld]
#ndb-nodeid=4
#server-id=4
user=mysql
ndbcluster
ndb-connectstring=10.80.1.117
datadir=/var/lib/mysql
[mysql_cluster]
ndb-connectstring=10.80.1.117



------------------------------------
#/etc/mysql/my.cnf @ 10.80.1.15
[mysqld]
user=mysql
ndbcluster
ndb-connectstring=10.80.1.117
datadir=/var/lib/mysql
[mysql_cluster]
ndb-connectstring=10.80.1.117




Part II-->2: start nodes

a)start ndb_mgmd@10.80.1.117:
bash-3.00# ndb_mgmd -f /etc/mysql/config.ini
2010-02-20 16:13:53 [MgmtSrvr] INFO -- NDB Cluster Management Server. mysql-5.1.39 ndb-7.0.9b
2010-02-20 16:13:55 [MgmtSrvr] INFO -- Reading cluster configuration from '/etc/mysql/config.ini'
bash-3.00#


b)start ndbd@10.80.1.15:
sunws05:/export/mysql# ndbd
2010-02-20 15:54:47 [ndbd] INFO -- Configuration fetched from '10.80.1.117:1186', generation: 1


c)start mysqld@10.80.1.117:



Part II-->3: show nodes info@10.80.1.117:


bash-3.00# ndb_mgm
ndb_mgm> show
Cluster Configuration
---------------------
[ndbd(NDB)] 2 node(s)
id=2 @10.80.1.15 (mysql-5.1.39 ndb-7.0.9, starting, Nodegroup: 0)
id=3 (not connected, accepting connect from 10.80.1.16)

[ndb_mgmd(MGM)] 1 node(s)
id=1 @10.80.1.117 (mysql-5.1.39 ndb-7.0.9)

[mysqld(API)] 2 node(s)
id=4 (not connected, accepting connect from 10.80.1.117)
id=5 (not connected, accepting connect from 10.80.1.15)

ndb_mgm>




Part II-->4: show log info@10.80.1.117:




bash-3.00# vi /var/lib/mysql/sunsvr12.err
------------->server-id is commented:
"/var/lib/mysql/sunsvr12.err" 43 lines, 2936 characters
100220 16:18:20 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql
100220 16:18:20 [Note] Plugin 'FEDERATED' is disabled.
InnoDB: The first specified data file ./ibdata1 did not exist:
InnoDB: a new database to be created!
100220 16:18:20 InnoDB: Setting file ./ibdata1 size to 10 MB
InnoDB: Database physically writes the file full: wait...
100220 16:18:21 InnoDB: Log file ./ib_logfile0 did not exist: new to be created
InnoDB: Setting log file ./ib_logfile0 size to 5 MB
InnoDB: Database physically writes the file full: wait...
100220 16:18:24 InnoDB: Log file ./ib_logfile1 did not exist: new to be created
InnoDB: Setting log file ./ib_logfile1 size to 5 MB
InnoDB: Database physically writes the file full: wait...
InnoDB: Doublewrite buffer not found: creating new
InnoDB: Doublewrite buffer created
InnoDB: Creating foreign key constraint system tables
InnoDB: Foreign key constraint system tables created
100220 16:18:30 InnoDB: Started; log sequence number 0 0
100220 16:18:30 [Note] NDB: NodeID is 4, management server '10.80.1.117:1186'
100220 16:18:31 [Note] NDB[0]: NodeID: 4, no storage nodes connected (timed out)
100220 16:18:31 [Warning] NDB: server id set to zero will cause any other mysqld with bin log to log with wrong server id
100220 16:18:31 [Note] Starting Cluster Binlog Thread
100220 16:18:31 [Note] Event Scheduler: Loaded 0 events
100220 16:18:49 [Warning] NDB : Tables not available after 15 seconds. Consider increasing --ndb-wait-setup value
100220 16:18:49 [Note] /opt/mysql/mysql/bin/mysqld: ready for connections.
Version: '5.1.39-ndb-7.0.9-cluster-gpl' socket: '/tmp/mysql.sock' port: 3306 MySQL Cluster Server (GPL)



------------->server-id is set to 4:

100220 16:26:56 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql
100220 16:26:58 [Note] Plugin 'FEDERATED' is disabled.
InnoDB: The log sequence number in ibdata files does not match
InnoDB: the log sequence number in the ib_logfiles!
100220 16:26:58 InnoDB: Database was not shut down normally!
InnoDB: Starting crash recovery.
InnoDB: Reading tablespace information from the .ibd files...
InnoDB: Restoring possible half-written data pages from the doublewrite
InnoDB: buffer...
100220 16:26:59 InnoDB: Started; log sequence number 0 44233
100220 16:26:59 [Note] NDB: NodeID is 4, management server '10.80.1.117:1186'
100220 16:27:00 [Note] NDB[0]: NodeID: 4, no storage nodes connected (timed out)
100220 16:27:00 [Warning] NDB: server id set to zero will cause any other mysqld with bin log to log with wrong server id
100220 16:27:00 [Note] Starting Cluster Binlog Thread
100220 16:27:00 [Note] Event Scheduler: Loaded 0 events
100220 16:27:17 [Warning] NDB : Tables not available after 15 seconds. Consider increasing --ndb-wait-setup value
100220 16:27:17 [Note] /opt/mysql/mysql/bin/mysqld: ready for connections.
Version: '5.1.39-ndb-7.0.9-cluster-gpl' socket: '/tmp/mysql.sock' port: 3306 MySQL Cluster Server (GPL)







You can see that SQL NODE is started, but does NOT join the cluster.
I tried similar configuraiotn on two redhat EL 5.3 servers, everything is OK, even when server-id is NOT set!!!
3#
 楼主| 发表于 2010-2-25 09:07:49 | 只看该作者
上面安装一切看起来正常,可是SQL节点就是无法加入到cluster中,我研究了2个多星期了,一直没有结果。

下面的内容是我另外的一种做法,请朋友们帮帮我分析下,万分感谢!那么多论坛,就这个中文的好像还活跃一点。
2#
 楼主| 发表于 2010-2-25 09:05:44 | 只看该作者
-------------------------------------


6. start cluster:
6.1 start management node:
sunws05:/etc/mysql# ndb_mgmd -f /etc/mysql/config.ini
2010-02-12 13:15:42 [MgmtSrvr] INFO -- NDB Cluster Management Server. mysql-5.1.39 ndb-7.0.9b
2010-02-12 13:15:43 [MgmtSrvr] INFO -- Reading cluster configuration from '/etc/mysql/config.ini'
2010-02-12 13:15:43 [MgmtSrvr] WARNING -- at line 20: Cluster configuration warning:
arbitrator with id 1 and db node with id 2 on same host 10.80.1.15
Running arbitrator on the same host as a database node may cause complete cluster shutdown in case of host failure.
2010-02-12 13:15:44 [MgmtSrvr] INFO -- Reading cluster configuration from '/etc/mysql/config.ini'
2010-02-12 13:15:44 [MgmtSrvr] WARNING -- at line 20: Cluster configuration warning:
arbitrator with id 1 and db node with id 2 on same host 10.80.1.15
Running arbitrator on the same host as a database node may cause complete cluster shutdown in case of host failure.
sunws05:/etc/mysql#

6.1.1 show cluster file/dir info:
a)
sunws05:/etc/mysql# cd /export/mysql/mysql-cluster
sunws05:/export/mysql/mysql-cluster# ls
ndb_1.pid ndb_1_cluster.log ndb_1_out.log
b)
sunws05:/export/mysql/mysql-cluster# cd /opt/mysql/mysql/mysql-cluster
sunws05:/opt/mysql/mysql/mysql-cluster# ls
ndb_1_config.bin.1

6.1.2 show cluster process info:
a)
sunws05:/opt/mysql/mysql/mysql-cluster# ps -ef | grep mysql
root 12694 22979 0 13:23:18 pts/3 0:00 grep mysql
root 12163 1 0 13:15:44 ? 0:04 ndb_mgmd -f /etc/mysql/config.ini

b)
sunws05:/opt/mysql/mysql/mysql-cluster# ps -ef | grep ndb
root 9622 1 0 17:47:15 ? 0:00 ndbd
root 12696 22979 0 13:23:24 pts/3 0:00 grep ndb
root 9623 9622 1 17:47:15 ? 20:33 ndbd
root 12163 1 0 13:15:44 ? 0:04 ndb_mgmd -f /etc/mysql/config.ini

6.1.3 cluster info:

sunws05:/opt/mysql/mysql/mysql-cluster# ndb_mgm
-- NDB Cluster -- Management Client --
ndb_mgm> show
Connected to Management Server at: 10.80.1.15:1186
Cluster Configuration
---------------------
[ndbd(NDB)] 2 node(s)
id=2 @10.80.1.15 (mysql-5.1.39 ndb-7.0.9, starting, Nodegroup: 0)
id=3 (not connected, accepting connect from 10.80.1.16)

[ndb_mgmd(MGM)] 1 node(s)
id=1 @10.80.1.15 (mysql-5.1.39 ndb-7.0.9)

[mysqld(API)] 2 node(s)
id=4 (not connected, accepting connect from 10.80.1.15)
id=5 (not connected, accepting connect from any host)

ndb_mgm>


6.2 start data node:
sunws05:/# ndbd
2010-02-12 13:51:52 [ndbd] INFO -- Configuration fetched from '10.80.1.15:1186', generation: 1

6.2.1 show data node info:
sunws05:/# ndb_mgm
-- NDB Cluster -- Management Client --
ndb_mgm> show
Connected to Management Server at: 10.80.1.15:1186
Cluster Configuration
---------------------
[ndbd(NDB)] 2 node(s)
id=2 @10.80.1.15 (mysql-5.1.39 ndb-7.0.9, starting, Nodegroup: 0)
id=3 (not connected, accepting connect from 10.80.1.16)

[ndb_mgmd(MGM)] 1 node(s)
id=1 @10.80.1.15 (mysql-5.1.39 ndb-7.0.9)

[mysqld(API)] 2 node(s)
id=4 (not connected, accepting connect from 10.80.1.15)
id=5 (not connected, accepting connect from any host)

ndb_mgm>

6.3 start SQL node:
sunws05:/# mysqld_safe &

6.3.1 show error file:
sunws05:/var/lib/mysql/mysql# vi /var/lib/mysql/sunws05.err
"/var/lib/mysql/sunws05.err" 25 lines, 1682 characters
100212 13:53:43 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql
100212 13:53:43 [Note] Plugin 'FEDERATED' is disabled.
InnoDB: The first specified data file ./ibdata1 did not exist:
InnoDB: a new database to be created!
100212 13:53:43 InnoDB: Setting file ./ibdata1 size to 10 MB
InnoDB: Database physically writes the file full: wait...
100212 13:53:44 InnoDB: Log file ./ib_logfile0 did not exist: new to be created
InnoDB: Setting log file ./ib_logfile0 size to 5 MB
InnoDB: Database physically writes the file full: wait...
100212 13:53:44 InnoDB: Log file ./ib_logfile1 did not exist: new to be created
InnoDB: Setting log file ./ib_logfile1 size to 5 MB
InnoDB: Database physically writes the file full: wait...
InnoDB: Doublewrite buffer not found: creating new
InnoDB: Doublewrite buffer created
InnoDB: Creating foreign key constraint system tables
InnoDB: Foreign key constraint system tables created
100212 13:53:45 InnoDB: Started; log sequence number 0 0
100212 13:53:45 [Note] NDB: NodeID is 4, management server '10.80.1.15:1186'
100212 13:53:46 [Note] NDB[0]: NodeID: 4, no storage nodes connected (timed out)
100212 13:53:46 [Warning] NDB: server id set to zero will cause any other mysqld with bin log to log with wrong server id
100212 13:53:46 [Note] Starting Cluster Binlog Thread
100212 13:53:46 [Note] Event Scheduler: Loaded 0 events
100212 13:54:01 [Warning] NDB : Tables not available after 15 seconds. Consider increasing --ndb-wait-setup value
100212 13:54:01 [Note] /opt/mysql/mysql/bin/mysqld: ready for connections.
Version: '5.1.39-ndb-7.0.9-cluster-gpl' socket: '/tmp/mysql.sock' port: 3306 MySQL Cluster Server (GPL)
~~~~~~~~we can see that mysqld is stared!!! but it does NOT work, i'll show you later.

6.3.2 show cluster info:
sunws05:/# ndb_mgm
-- NDB Cluster -- Management Client --
ndb_mgm> show
Connected to Management Server at: 10.80.1.15:1186
Cluster Configuration
---------------------
[ndbd(NDB)] 2 node(s)
id=2 @10.80.1.15 (mysql-5.1.39 ndb-7.0.9, starting, Nodegroup: 0)
id=3 (not connected, accepting connect from 10.80.1.16)

[ndb_mgmd(MGM)] 1 node(s)
id=1 @10.80.1.15 (mysql-5.1.39 ndb-7.0.9)

[mysqld(API)] 2 node(s)
id=4 (not connected, accepting connect from 10.80.1.15)
id=5 (not connected, accepting connect from any host)

ndb_mgm>

~~~~~~we can see, SQL node does NOT join the mysql cluster!!!


6.3.3 Now, let's see the error file[/var/lib/mysql/sunws05.err] again, i find that below contents are added:
100212 14:00:12 [Warning] NDB: Could not acquire global schema lock (4009)Cluster Failure
100212 14:03:15 [Warning] NDB: Could not acquire global schema lock (4009)Cluster Failure
100212 14:03:53 [Warning] NDB: Could not acquire global schema lock (4009)Cluster Failure

6.3.4 create DB:
mysql> CREATE TABLE Persons(
-> Id_P int,
-> LastName varchar(255),
-> FirstName varchar(255),
-> Address varchar(255),
-> City varchar(255)
-> )ENGINE=NDBCLUSTER;
ERROR 1005 (HY000): Can't create table 'genview.Persons' (errno: 157)
您需要登录后才可以回帖 登录 | 注册

本版积分规则

QQ|Archiver|小黑屋|手机版|MariaDB社区 ( 京ICP备07012489号    |
业务联系: QQ:48474881; 邮箱: 48474881@qq.com; 电话:13911732319
声明:本站部分文章是网友转载,若未经作者同意或署名有误,请联系网站管理员。

GMT+8, 2024-11-1 18:32 , Processed in 0.063568 second(s), 21 queries .

Powered by Discuz! X3.2

© 2001-2013 Comsenz Inc.

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