Hello,

I will have to upgrade from 7.0.7 to 7.1.4b (on Solaris 10 x86) and do not want to miss a bit...


From reading, this seems to be straight forward, but the devil might be in the details.

What I will do:
- create a backup ;-)
- extracting the tar file to a directory
- changing the symlink to the new directory
- stop all cluster nodes, mysqld and manager processes
- start Manager
- start data Nodes
- start mysqld

Is stopping the hole system the best option to be save? ...or is it fine to
- stop both manager
- start both manager
- rolling restart of all mysqld
- rolling restart of all data nodes
in that order?


Do I only have to "ATER TABLE <tablename>" for each table to get the new functionalities (NDB-native default values)? Or what exact parameters do I have to apply? Do I need the 'SET DEFAULT' parameter for each default value to change this?


Is there a list of configuration parameters, worth to have a look, to get the most out of the new release? What do i definitivly have to chane in the confoguration?

Thank You.

Stefan




My System:
6 Data nodes, 3 node groups, on 6 systems
6 mysqld on the same systems
2 manager
2 mysqld on the managers
6 systems with the applications, connecting the 6 mysqld on the 6 data nodes

It is mentioned in Mysql site that for clustering all nodes should be connected by LAN please explain whether mysql clustering is possible on WAN or not

Hi All

I have a 4 node cluster setup

ips are 192.168.0.2, 192.168.0.3, 192.168.0.7, and 192.168.0.8

the management node is at 192.168.0.25

the my.cnf file for the SQL nodes contains

[mysqld]
# IP address of the cluster management node
ndbcluster
ndb-connectstring=192.168.0.25

[mysql_cluster]
ndb-connectstring=192.168.0.25



the management node config.ini contains


#
[ndbd default]
NoOfReplicas= 4
MaxNoOfConcurrentOperations= 10000
DataMemory= 80M
IndexMemory= 24M

[tcp default]

[ndb_mgmd default]
DataDir= /var/lib/mysql-cluster

[ndb_mgmd]
Id=1
HostName= 192.168.0.25
datadir= /var/lib/mysql-cluster

[ndbd]
Id= 2
HostName= 192.168.0.2

[ndbd]
Id= 3
HostName= 192.168.0.3

[ndbd]
Id= 4
HostName= 192.168.0.7

[ndbd]
Id= 5
HostName= 192.168.0.8

[mysqld]
Id= 6
HostName= 192.168.0.2

[mysqld]
Id= 7
HostName= 192.168.0.3

[mysqld]
Id= 8
HostName= 192.168.0.7

[mysqld]
Id= 9
HostName= 192.168.0.8

[mysqld]


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

the sql nodes were started using the following commands

shell> /usr/local/mysql/bin/mysqld_safe --user=mysql --ndbcluster --ndb-connectstring=192.168.0.25&

shell> /usr/local/mysql/bin/ndbd --initial

shell> /usr/local/mysql/support-files/mysql.server start


my problem is that when i look at the management node and run a show in
/usr/local/mysql/bin/ndb_mgm

all i see is the entries in the datanodes.. none of the mysqld entries show

on looking at the log in each server this is what i find


100722 08:53:37 mysqld_safe Starting mysqld daemon with databases from /usr/local/mysql/data
100722 8:53:37 [Note] Plugin 'FEDERATED' is disabled.
100722 8:53:37 InnoDB: Started; log sequence number 0 44233
100722 8:53:37 [Note] NDB: NodeID is 7, management server '192.168.0.25:1186'
100722 8:53:38 [Note] NDB[0]: NodeID: 7, no storage nodes connected (timed out)
100722 8:53:38 [Note] Starting Cluster Binlog Thread
100722 8:53:38 [Note] Event Scheduler: Loaded 0 events
100722 8:53:53 [Warning] NDB : Tables not available after 15 seconds. Consider
100722 8:53:53 [Note] /usr/local/mysql/bin/mysqld: ready for connections.


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

i am on ubuntu using the tutorial presented here (my servers are dual processor with 4gb ram each)

http://dev.mysql.com/doc/refman/5.1/en/mysql-cluster-multi-computer.html

the binary used is mysql-cluster-gpl-7.1.4b-linux-x86_64-glibc23.tar.gz

with obvious changes ie.. all my nodes are data+mysqld nodes

Any and all Help would be welcome

Thanks and Regards

Cirvesh

I can read from the changelog and see on a lot of examples on mysql.com that mysql-cluster-5.1.47-ndb-7.1.5 appearently was released on the 25 of june - but 7.1.4b is listed as the GA version.

Why is 7.1.5 not the GA version? (and it's not even in the download section)

hi,

by default, tables in ndb are created as STORAGE MEMORY. Is there any way to change the default to "STORAGE DISK" and assign with a default tablespace?

for my use case, I'm evaluating if MySQL cluster could be provided in a hosting environment. It's cheaper to store data on disk than in memory. :-)

I have successfully installed MySQL Cluster 7.1.4b on a few servers for testing. I have the NDBD nodes connected to the Management Server, and the MySQL API's connected to the Management Server. So far everything works very well. This is an otherwise fresh installation of CentOS 5.5 x64.

I installed MySQL Cluster by downloading the RPM's for RHEL 5 x64, and running rpm -Uhv on the client, server, shared, storage, and tools, as well as management on the management server. This installed the appropriate packages without issue.

When I try to install any packages through yum which depend on MySQL, it fails. For example, when I try to install Apache and PHP (with the php-mysql connector), I get this error message:
=================== BEGIN OUTPUT ======================
[root@ast01 ~]# yum install httpd php php-mysql
Loaded plugins: fastestmirror
Loading mirror speeds from cached hostfile
* addons: mirror.5ninesolutions.com
* base: mirror.stanford.edu
* extras: linux.mirrors.es.net
* updates: mirror.singleedge.com
addons | 951 B 00:00
base | 2.1 kB 00:00
extras | 2.1 kB 00:00
updates | 1.9 kB 00:00
updates/primary_db | 418 kB 00:00
Setting up Install Process
Package httpd-2.2.3-43.el5.centos.x86_64 already installed and latest version
Resolving Dependencies
--> Running transaction check
---> Package php.x86_64 0:5.1.6-27.el5 set to be updated
--> Processing Dependency: php-common = 5.1.6-27.el5 for package: php
--> Processing Dependency: php-cli = 5.1.6-27.el5 for package: php
---> Package php-mysql.x86_64 0:5.1.6-27.el5 set to be updated
--> Processing Dependency: php-pdo for package: php-mysql
--> Processing Dependency: libmysqlclient.so.15(libmysqlclient_15)(64bit) for package: php-mysql
--> Processing Dependency: libmysqlclient.so.15()(64bit) for package: php-mysql
--> Running transaction check
---> Package mysql.x86_64 0:5.0.77-4.el5_5.3 set to be updated
--> Processing Dependency: perl(DBI) for package: mysql
---> Package php-cli.x86_64 0:5.1.6-27.el5 set to be updated
---> Package php-common.x86_64 0:5.1.6-27.el5 set to be updated
---> Package php-pdo.x86_64 0:5.1.6-27.el5 set to be updated
--> Running transaction check
---> Package perl-DBI.x86_64 0:1.52-2.el5 set to be updated
--> Processing Conflict: MySQL-Cluster-gpl-server conflicts mysql
--> Finished Dependency Resolution
MySQL-Cluster-gpl-server-7.1.4b-1.rhel5.x86_64 from installed has depsolving problems
--> MySQL-Cluster-gpl-server conflicts with mysql
Error: MySQL-Cluster-gpl-server conflicts with mysql
You could try using --skip-broken to work around the problem
You could try running: package-cleanup --problems
package-cleanup --dupes
rpm -Va --nofiles --nodigest
The program package-cleanup is found in the yum-utils package.
[root@ast01 ~]#
==================== END OUTPUT =======================

What can I do to resolve this issue and allow my installation of MySQL Cluster to work properly in this situation?

Thanks in advance,
Brett

I installed MySQL Cluster successful.
There are three servers, two of them used as sql nodes and data nodes. The last one used as management node.

My question is:
How to use php connect mysql cluster node?
Which node's ip should i use in my php code?

Mysql cluseter :mysql-cluster-gpl-7.1.4b-win32
os: windows 2003 server

Thanks in advance,
davidli

Hello guys

I am a software developer, please bear with me for any confusion I may cause.

I have a current project that need to centralised data and also to distribute data to each branch. To illustrate the situation:

a) I have HQ (headquarters) that wants a consolidated data for all their branches.

b) Each branch stores data pertaining to their branch only (and global data as well) .

c) When record being added or updated at any of the branch, data has to be reflected at HQ as well.

d) Any record changes at HQ (for certain branch) must be reflected at the particular branch db.

In programming way, it can be done, but it may not be as efficient as the RDBMS itself managing the data. So, I would like to ask from fellow MySQL users/guru, is there a way to implement such mechanism using MySQL?

Thanks in advance.

I've seen the recommendations not to run NDB nodes virtualized, but how about
the management node(s) ?

/P

I'm trying to run ndb in diskless=1 mode, but keep the table definitions intact across restarts. With diskless=0, it all works fine, but consumes a lot of space in ndb_data/ndb_1_fs/. None of the actual data needs to survive a reboot, and I'd like the speed of not writing anything to disk at all.

So I thought using init-file=filename.sql that has a bunch of create table statements would work. That way, the empty tables exist upon start, and the app can simply populate it as needed.

However, no tables are created. Various other statements (eg: "SET GLOBAL ndb_table_no_logging = 1;") seems to work (apparently a variable I cannot set in my.cnf??)

I was wondering if it's a problem with the order in which mysqld uses these commands? Does it execute the init-file before mysqld is ready for create table commands?

The init-file is:
SET GLOBAL ndb_table_no_logging = 1;
CREATE TABLE aa ( id smallint(6) NOT NULL DEFAULT '0', runtime int(11) NOT NULL DEFAULT '0', PRIMARY KEY idx1 (id) USING HASH) ENGINE=NDB;

The documentation says one command per line and no comments, so that create table is one long line up to the semicolon

Thank you,
PH

Hello,

I need to make a decision between replication Vs. cluster for one my clients project. My clients application uses lot of foreign keys. Therefore InnoDB is the only option at the moment and to go for replication.

I need to know, if there is any news/predictions/possibility to have foreign key functionality for NDB tables in the near future? In that case we can still think of having cluster in the later phase of project.

Thanks in advance,

Sameer Deshpande.

Hello,

I've got some problems with a statement on ndb (7.09/ubuntu):

select * from kurse1 where wkn = '696960' and datum in (select max(datum) from kurse1 where wkn = '696960' group by substring(datum,1,7) order by datum desc) order by datum desc

With myisam-tables it takes about 10 sec, but with ndb it takes about 3:30min. Can someone explain this to me? What can I do to boost queries like this?

Explain extended says the following:

+----+--------------------+--------+------+----------------------+--------+---------+-------+------+----------+----------------------------------------------+
| id | select_type | table | type | possible_keys | key | key_len | ref | rows | filtered | Extra |
+----+--------------------+--------+------+----------------------+--------+---------+-------+------+----------+----------------------------------------------+
| 1 | PRIMARY | kurse1 | ref | UNIQUE,WKN_DATUM,WKN | UNIQUE | 8 | const | 10 | 100.00 | Using where |
| 2 | DEPENDENT SUBQUERY | kurse1 | ref | UNIQUE,WKN_DATUM,WKN | UNIQUE | 8 | const | 10 | 100.00 | Using where; Using temporary; Using filesort


Thanks a lot.

Hey there,

We have a production installation (2 x ndbmtd, 1 x ndb_mgmd, 24 x mysqld) and it's working nicely.

However, the data schema was migrated directly from an old MyISAM installation and a TEXT field is being used on a table which has a lot of inserts, selects and updates. I believe that under NDB this is inefficient.

The TEXT data-type was originally chosen as at the time MySQL had a limit of VARCHAR(255) and we needed to store longer strings.

The table has approximately 6 million rows and about 1.2 million transactions per day.

What's the best way to convert the data-type to VARCHAR(2048)? Is an online ALTER TABLE statment a viable option? If so, would it require double the RAM that the current table uses (as ALTER TABLE often makes a copy first before renaming)? Would it take a long time, and would the database be accessible for reads AND writes during the execution of the statement?

I'd prefer to avoid any downtime if possible, so your advice and suggestions would be appreciated.

Hi,

I've started getting the following error when trying to run a program which loads data into NDB tables:

Unable to execute query: Got temporary error 233 'Out of operation records in transaction coordinator (increase MaxNoOfConcurrentOperations)' from NDBCLUSTER. ERROR: Got temporary error 233 'Out of operation records in transaction coordinator (increase MaxNoOfConcurrentOperations)' from NDBCLUSTER

My problem is that MaxNoOfConcurrentOperations is set to 1,000,000 already and the program which I'm running should be the only one doing any kind of operation on this database, and it only makes 4 database calls every time it runs.

How can I check what other programs/processes are accessing the database and causing this error?

Also, am I on the right track in thinking that it must be another process causing the MaxNoOfConcurrentOperations to be exceeded? The program has crashed in the middle of queries before, could it be possible that these previous queries are still holding on to their operations lock?

Thank you

I am working on MySql 5.1.35 with cluster packages ver

- MySQL-Cluster-gpl-management-7.1.5-1.rhel5.i386.rpm
- MySQL-Cluster-gpl-storage-7.1.5-1.rhel5.i386.rpm
- MySQL-Cluster-gpl-tools-7.1.5-1.rhel5.i386.rpm

for cluster. But when i start the sql on node i get

Starting MySQL...Manager of pid-file quit without updating [FAILED]
and in : /var/lib/mysql/localhost.localdomain.err

100811 17:41:06 InnoDB: Starting shutdown...
100811 17:41:08 InnoDB: Shutdown completed; log sequence number 0 46409
100811 17:41:08 [Warning] Forcing shutdown of 1 plugins
100811 17:41:08 [Note] /usr/sbin/mysqld: Shutdown complete

100811 17:41:08 mysqld_safe mysqld from pid file /var/lib/mysql/localhost.localdomain.pid ended
100811 17:56:42 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql
100811 17:56:45 InnoDB: Started; log sequence number 0 46409
100811 17:56:45 [ERROR] /usr/sbin/mysqld: unknown option '--ndbcluster'
100811 17:56:45 [ERROR] Aborting

100811 17:56:45 InnoDB: Starting shutdown...
100811 17:56:47 InnoDB: Shutdown completed; log sequence number 0 46409
100811 17:56:47 [Warning] Forcing shutdown of 1 plugins
100811 17:56:47 [Note] /usr/sbin/mysqld: Shutdown complete

100811 17:56:47 mysqld_safe mysqld from pid file /var/lib/mysql/localhost.localdomain.pid ended
100811 18:05:57 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql
100811 18:06:01 InnoDB: Started; log sequence number 0 46409
100811 18:06:01 [ERROR] /usr/sbin/mysqld: unknown option '--ndbcluster'
100811 18:06:01 [ERROR] Aborting

------------------------------------------------------------------------------
my.cnf file contains::


# Options for mysqld process:
[mysql.server]
dir=/var/lib/mysql
socket=/var/lib/mysql/mysql.sock

[mysqld]
datadir=/var/lib/mysql
socket=/var/lib/mysql/mysql.sock

[mysql]
socket=/var/lib/mysql/mysql.sock

[MYSQLD]
ndbcluster # run NDB storage engine
ndb-connectstring=172.16.20.14 # location of management server
# Options for ndbd process:

ndb-mgmd-host=172.16.20.14
#ndb-nodeid=5 #this caused the ndbcluster engine to not be loaded by the plugin - see
log
engine_condition_pushdown=1 # send WHERE statements to Data Nodes for
evaluation

[NDBD]
ndbd-host=172.16.20.14
ndb-nodeid=2
[NDBD]
ndbd-host=172.16.20.14
ndb-nodeid=3

[NDB_MGMD]
ndb-mgmd-host=172.16.20.14
ndb-nodeid=4

[MYSQL_CLUSTER]
ndb-connectstring=172.16.20.14 # location of management server
---------------------------------------------------------------------------------

I am using the NDB Cluster 7.1.5-1. I just can not create the sample database WORLD.

When I do show processlist, I found:

mysql> show processlist;
+----+-------------+----------------+------+---------+-------+---------------------------------+------------------+
| Id | User | Host | db | Command | Time | State | Info |
+----+-------------+----------------+------+---------+-------+---------------------------------+------------------+
| 1 | system user | | NULL | Daemon | 15816 | Waiting for ndbcluster to start | NULL |
| 18 | root | mgmtnode:38755 | NULL | Query | 0 | NULL | show processlist |
+----+-------------+----------------+------+---------+-------+---------------------------------+------------------+
2 rows in set (0.00 sec)

Looking at the error log, I found:

100818 16:06:03 [ERROR] NDB: CREATE TABLE IF NOT EXISTS mysql.ndb_apply_status ( server_id INT UNSIGNED NOT NULL, epoch BIGINT UNSIGNED NOT NULL, log_name VARCHAR(255) BINARY NOT NULL, start_pos BIGINT UNSIGNED NOT NULL, end_pos BIGINT UNSIGNED NOT NULL, PRIMARY KEY USING HASH (server_id) ) ENGINE=NDB CHARACTER SET latin1: error Can't create table 'mysql.ndb_apply_status' (errno: 157) 1005(ndb: 0) 1 1

Can some one tell me what is wrong with my installation ? I notice that althoug I have 2 data nodes, but the show global status indicates that only 1 datanode is ready !!!!!!!!!


Here is my config:

/usr/mysql-cluster#> ndb_mgm
-- NDB Cluster -- Management Client --
ndb_mgm> show
Connected to Management Server at: 192.168.20.100:1186
Cluster Configuration
---------------------
[ndbd(NDB)] 2 node(s)
id=2 @192.168.20.101 (mysql-5.1.47 ndb-7.1.5, Nodegroup: 0, Master)
id=3 @192.168.20.102 (mysql-5.1.47 ndb-7.1.5, Nodegroup: 0)

[ndb_mgmd(MGM)] 1 node(s)
id=1 @192.168.20.100 (mysql-5.1.47 ndb-7.1.5)

[mysqld(API)] 4 node(s)
id=4 @192.168.20.100 (mysql-5.1.47 ndb-7.1.5)
id=5 (not connected, accepting connect from any host)
id=6 @192.168.20.100 (mysql-5.1.47 ndb-7.1.5)
id=7 (not connected, accepting connect from any host)

And in mysql:
mysql> show global status like 'NDB%';
+--------------------------------+----------------+
| Variable_name | Value |
+--------------------------------+----------------+
| Ndb_cluster_node_id | 5 |
| Ndb_config_from_host | 192.168.20.100 |
| Ndb_config_from_port | 1186 |
| Ndb_number_of_data_nodes | 2 |
| Ndb_number_of_ready_data_nodes | 1 |
| Ndb_connect_count | 2 |
| Ndb_execute_count | 0 |

mysql> show engine ndb status;
+------------+-----------------------+-------------------------------------------------------------------------------------------------------------------------------------------------+
| Type | Name | Status |
+------------+-----------------------+-------------------------------------------------------------------------------------------------------------------------------------------------+
| ndbcluster | connection | cluster_node_id=5, connected_host=192.168.20.100, connected_port=1186, number_of_data_nodes=2, number_of_ready_data_nodes=1, connect_count=2 |
| ndbcluster | NdbTransaction | created=2, free=2, sizeof=224 |
| ndbcluster | NdbOperation | created=4, free=4, sizeof=756 |
| ndbcluster | NdbIndexScanOperation | created=0, free=0, sizeof=888 |
| ndbcluster | NdbIndexOperation | created=0, free=0, sizeof=760 |
| ndbcluster | NdbRecAttr | created=0, free=0, sizeof=64 |
| ndbcluster | NdbApiSignal | created=16, free=16, sizeof=136 |
| ndbcluster | NdbLabel | created=0, free=0, sizeof=196 |
| ndbcluster | NdbBranch | created=0, free=0, sizeof=24 |
| ndbcluster | NdbSubroutine | created=0, free=0, sizeof=68 |
| ndbcluster | NdbCall | created=0, free=0, sizeof=16 |
| ndbcluster | NdbBlob | created=0, free=0, sizeof=344 |
| ndbcluster | NdbReceiver | created=0, free=0, sizeof=92 |
| ndbcluster | NdbLockHandle | created=0, free=0, sizeof=32 |
| ndbcluster | binlog | latest_epoch=0, latest_trans_epoch=29832842838022, latest_received_binlog_epoch=0, latest_handled_binlog_epoch=0, latest_applied_binlog_epoch=0 |
+------------+-----------------------+-------------------------------------------------------------------------------------------------------------------------------------------------+
15 rows in set (0.01 sec)

I try to install sizer fallow the [sizer home page:http://www.severalnines.com/sizer/index.php] step by step.
when i try to make src, i got an error.
fallow message:

[root@HAMC sizer-0.30]# sh autogen.sh

[root@HAMC sizer-0.30]# ./configure

checking for a BSD-compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
checking for gawk... gawk
checking whether make sets $(MAKE)... yes
checking for gawk... (cached) gawk
checking for gcc... gcc
checking for C compiler default output file name... a.out
checking whether the C compiler works... yes
checking whether we are cross compiling... no
checking for suffix of executables...
checking for suffix of object files... o
checking whether we are using the GNU C compiler... yes
checking whether gcc accepts -g... yes
checking for gcc option to accept ANSI C... none needed
checking for style of include used by make... GNU
checking dependency style of gcc... gcc3
checking for g++... g++
checking whether we are using the GNU C++ compiler... yes
checking whether g++ accepts -g... yes
checking dependency style of g++... gcc3
checking how to run the C preprocessor... gcc -E
checking whether make sets $(MAKE)... (cached) yes
checking for egrep... grep -E
checking for ANSI C header files... yes
checking for sys/types.h... yes
checking for sys/stat.h... yes
checking for stdlib.h... yes
checking for string.h... yes
checking for memory.h... yes
checking for strings.h... yes
checking for inttypes.h... yes
checking for stdint.h... yes
checking for unistd.h... yes
checking for stdlib.h... (cached) yes
checking for string.h... (cached) yes
checking for unistd.h... (cached) yes
checking for sys/stat.h... (cached) yes
checking for atoi... yes
checking build system type... x86_64-unknown-linux-gnu
checking host system type... x86_64-unknown-linux-gnu
checking for mysql_config executable... checking for mysql_config... mysql_config
checking for gcc... (cached) gcc
checking whether we are using the GNU C compiler... (cached) yes
checking whether gcc accepts -g... (cached) yes
checking for gcc option to accept ANSI C... (cached) none needed
checking dependency style of gcc... (cached) gcc3
checking whether we are using the GNU C++ compiler... (cached) yes
checking whether g++ accepts -g... (cached) yes
checking dependency style of g++... (cached) gcc3
ok
checking for ndbapi headers... found
configure: creating ./config.status
config.status: creating Makefile
config.status: creating src/Makefile
config.status: creating config.h
config.status: config.h is unchanged
config.status: executing depfiles commands

[root@HAMC sizer-0.30]# make

cd . && /bin/sh /opt/sizer-0.30/missing --run autoheader
rm -f stamp-h1
touch config.h.in
cd . && /bin/sh ./config.status config.h
config.status: creating config.h
config.status: config.h is unchanged
make all-recursive
make[1]: Entering directory `/opt/sizer-0.30'
Making all in src
make[2]: Entering directory `/opt/sizer-0.30/src'
g++ -Wall -fno-strict-aliasing -g -O2 -I/usr/include/mysql -g -pipe -Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector --param=ssp-buffer-size=4 -m64 -DUNIV_LINUX -I/usr/include/mysql/storage/ndb -I/usr/include/mysql/storage/ndb/ndbapi -I/usr/include/mysql/storage/ndb/mgmapi -I/usr/include/mysql/ndb -I/usr/include/mysql/ndb/ndbapi -I/usr/include/mysql/ndb/mgmapi -I/usr/include/mysql -rdynamic -L/usr/lib64/mysql -lmysqlclient_r -lz -lrt -lpthread -lcrypt -lnsl -lm -lpthread -lmygcc -lndbclient -lmystrings -lmysys -o sizer sizer.o
sizer.o: In function `select_count(Ndb*, NdbDictionary::Table const*, int, int*, NdbOperation::LockMode)':
/opt/sizer-0.30/src/sizer.cpp:1213: undefined reference to `NdbInterpretedCode::NdbInterpretedCode(NdbDictionary::Table const*, unsigned int*, unsigned int)'
/opt/sizer-0.30/src/sizer.cpp:1214: undefined reference to `NdbInterpretedCode::interpret_exit_last_row()'
/opt/sizer-0.30/src/sizer.cpp:1214: undefined reference to `NdbInterpretedCode::finalise()'
/opt/sizer-0.30/src/sizer.cpp:1229: undefined reference to `Ndb::startTransaction(NdbDictionary::Table const*, char const*, unsigned int)'
/opt/sizer-0.30/src/sizer.cpp:1241: undefined reference to `NdbDictionary::Table::getName() const'
/opt/sizer-0.30/src/sizer.cpp:1241: undefined reference to `NdbTransaction::getNdbScanOperation(char const*)'
/opt/sizer-0.30/src/sizer.cpp:1255: undefined reference to `NdbScanOperation::setInterpretedCode(NdbInterpretedCode const*)'
/opt/sizer-0.30/src/sizer.cpp:1264: undefined reference to `NdbDictionary::Column::ROW_COUNT'
/opt/sizer-0.30/src/sizer.cpp:1264: undefined reference to `NdbOperation::getValue(NdbDictionary::Column const*, char*)'
/opt/sizer-0.30/src/sizer.cpp:1265: undefined reference to `NdbDictionary::Column::ROW_SIZE'
/opt/sizer-0.30/src/sizer.cpp:1265: undefined reference to `NdbOperation::getValue(NdbDictionary::Column const*, char*)'
/opt/sizer-0.30/src/sizer.cpp:1266: undefined reference to `NdbTransaction::execute(NdbTransaction::ExecType, NdbOperation::AbortOption, int)'
/opt/sizer-0.30/src/sizer.cpp:1275: undefined reference to `NdbScanOperation::nextResult(bool, bool)'
/opt/sizer-0.30/src/sizer.cpp:1280: undefined reference to `NdbTransaction::getNdbError() const'
/opt/sizer-0.30/src/sizer.cpp:1283: undefined reference to `Ndb::closeTransaction(NdbTransaction*)'
/opt/sizer-0.30/src/sizer.cpp:1217: undefined reference to `NdbInterpretedCode::getNdbError() const'
/opt/sizer-0.30/src/sizer.cpp:1301: undefined reference to `NdbInterpretedCode::~NdbInterpretedCode()'
/opt/sizer-0.30/src/sizer.cpp:1231: undefined reference to `Ndb::getNdbError() const'
/opt/sizer-0.30/src/sizer.cpp:1257: undefined reference to `NdbTransaction::getNdbError() const'
/opt/sizer-0.30/src/sizer.cpp:1258: undefined reference to `Ndb::closeTransaction(NdbTransaction*)'
/opt/sizer-0.30/src/sizer.cpp:1249: undefined reference to `NdbTransaction::getNdbError() const'
/opt/sizer-0.30/src/sizer.cpp:1250: undefined reference to `Ndb::closeTransaction(NdbTransaction*)'
/opt/sizer-0.30/src/sizer.cpp:1293: undefined reference to `Ndb::closeTransaction(NdbTransaction*)'
/opt/sizer-0.30/src/sizer.cpp:1301: undefined reference to `NdbInterpretedCode::~NdbInterpretedCode()'
sizer.o: In function `calc_blob_column(NdbDictionary::Table const*, NdbDictionary::Index const*, int, Ndb*, int&, int&, bool)':
/opt/sizer-0.30/src/sizer.cpp:1084: undefined reference to `Ndb::startTransaction(NdbDictionary::Table const*, char const*, unsigned int)'
/opt/sizer-0.30/src/sizer.cpp:1085: undefined reference to `NdbTransaction::getNdbScanOperation(NdbDictionary::Table const*)'
/opt/sizer-0.30/src/sizer.cpp:1091: undefined reference to `NdbTransaction::execute(NdbTransaction::ExecType, NdbOperation::AbortOption, int)'
/opt/sizer-0.30/src/sizer.cpp:1104: undefined reference to `NdbDictionary::Table::getColumn(int) const'
/opt/sizer-0.30/src/sizer.cpp:1105: undefined reference to `NdbDictionary::Column::getPartSize() const'
/opt/sizer-0.30/src/sizer.cpp:1108: undefined reference to `NdbScanOperation::nextResult(bool, bool)'
/opt/sizer-0.30/src/sizer.cpp:1112: undefined reference to `NdbBlob::getNull(int&)'
/opt/sizer-0.30/src/sizer.cpp:1133: undefined reference to `NdbScanOperation::close(bool, bool)'
/opt/sizer-0.30/src/sizer.cpp:1134: undefined reference to `NdbTransaction::close()'
/opt/sizer-0.30/src/sizer.cpp:1159: undefined reference to `NdbDictionary::Column::getStorageType() const'
/opt/sizer-0.30/src/sizer.cpp:1116: undefined reference to `NdbBlob::getLength(unsigned long long&)'
/opt/sizer-0.30/src/sizer.cpp:1133: undefined reference to `NdbScanOperation::close(bool, bool)'
/opt/sizer-0.30/src/sizer.cpp:1134: undefined reference to `NdbTransaction::close()'
/opt/sizer-0.30/src/sizer.cpp:1138: undefined reference to `NdbDictionary::Column::getStorageType() const'
/opt/sizer-0.30/src/sizer.cpp:1095: undefined reference to `NdbScanOperation::close(bool, bool)'
/opt/sizer-0.30/src/sizer.cpp:1096: undefined reference to `NdbTransaction::close()'
/opt/sizer-0.30/src/sizer.cpp:1104: undefined reference to `NdbDictionary::Table::getColumn(int) const'
/opt/sizer-0.30/src/sizer.cpp:1105: undefined reference to `NdbDictionary::Column::getPartSize() const'
sizer.o: In function `calc_var_column(NdbDictionary::Table const*, NdbDictionary::Index const*, int, Ndb*, bool, bool, bool)':
/opt/sizer-0.30/src/sizer.cpp:977: undefined reference to `Ndb::startTransaction(NdbDictionary::Table const*, char const*, unsigned int)'
/opt/sizer-0.30/src/sizer.cpp:982: undefined reference to `NdbTransaction::getNdbScanOperation(NdbDictionary::Table const*)'
/opt/sizer-0.30/src/sizer.cpp:985: undefined reference to `NdbOperation::getValue(unsigned int, char*)'
/opt/sizer-0.30/src/sizer.cpp:991: undefined reference to `NdbDictionary::Table::getColumn(int) const'
/opt/sizer-0.30/src/sizer.cpp:992: undefined reference to `NdbDictionary::Column::getType() const'
/opt/sizer-0.30/src/sizer.cpp:1019: undefined reference to `NdbTransaction::execute(NdbTransaction::ExecType, NdbOperation::AbortOption, int)'
/opt/sizer-0.30/src/sizer.cpp:1030: undefined reference to `NdbScanOperation::nextResult(bool, bool)'
/opt/sizer-0.30/src/sizer.cpp:1051: undefined reference to `NdbTransaction::close()'
/opt/sizer-0.30/src/sizer.cpp:1051: undefined reference to `NdbTransaction::close()'
/opt/sizer-0.30/src/sizer.cpp:1056: undefined reference to `NdbDictionary::Table::getColumn(int) const'
/opt/sizer-0.30/src/sizer.cpp:1056: undefined reference to `NdbDictionary::Column::getSizeInBytes() const'
/opt/sizer-0.30/src/sizer.cpp:996: undefined reference to `NdbDictionary::Column::getCharset() const'
/opt/sizer-0.30/src/sizer.cpp:1023: undefined reference to `NdbTransaction::close()'
sizer.o: In function `waste(NdbDictionary::Column const*)':
/opt/sizer-0.30/src/sizer.cpp:444: undefined reference to `NdbDictionary::Column::getSizeInBytes() const'
sizer.o: In function `calculate_dm_ui(Ndb*, NdbDictionary::Table const*, NdbDictionary::Index const*, int&, int&, bool, int&, int&, bool&)':
/opt/sizer-0.30/src/sizer.cpp:665: undefined reference to `NdbDictionary::Index::getNoOfColumns() const'
/opt/sizer-0.30/src/sizer.cpp:685: undefined reference to `NdbDictionary::Index::getColumn(unsigned int) const'
/opt/sizer-0.30/src/sizer.cpp:686: undefined reference to `NdbDictionary::Column::getName() const'
/opt/sizer-0.30/src/sizer.cpp:686: undefined reference to `NdbDictionary::Table::getColumn(char const*) const'
/opt/sizer-0.30/src/sizer.cpp:686: undefined reference to `NdbDictionary::Column::getColumnNo() const'
/opt/sizer-0.30/src/sizer.cpp:689: undefined reference to `NdbDictionary::Column::getType() const'
/opt/sizer-0.30/src/sizer.cpp:698: undefined reference to `NdbDictionary::Column::getPrimaryKey() const'
/opt/sizer-0.30/src/sizer.cpp:760: undefined reference to `NdbDictionary::Column::getStorageType() const'
/opt/sizer-0.30/src/sizer.cpp:763: undefined reference to `NdbDictionary::Column::getSizeInBytes() const'
/opt/sizer-0.30/src/sizer.cpp:771: undefined reference to `NdbDictionary::Column::getNullable() const'
/opt/sizer-0.30/src/sizer.cpp:718: undefined reference to `NdbDictionary::Column::getSizeInBytes() const'
/opt/sizer-0.30/src/sizer.cpp:719: undefined reference to `NdbDictionary::Column::getStorageType() const'
/opt/sizer-0.30/src/sizer.cpp:761: undefined reference to `NdbDictionary::Column::getSizeInBytes() const'
/opt/sizer-0.30/src/sizer.cpp:732: undefined reference to `NdbDictionary::Column::getStorageType() const'
/opt/sizer-0.30/src/sizer.cpp:727: undefined reference to `NdbDictionary::Column::getLength() const'
/opt/sizer-0.30/src/sizer.cpp:743: undefined reference to `NdbDictionary::Column::getStorageType() const'
/opt/sizer-0.30/src/sizer.cpp:700: undefined reference to `NdbDictionary::Column::getName() const'
/opt/sizer-0.30/src/sizer.cpp:694: undefined reference to `NdbDictionary::Column::getNullable() const'
/opt/sizer-0.30/src/sizer.cpp:694: undefined reference to `NdbDictionary::Column::getStorageType() const'
/opt/sizer-0.30/src/sizer.cpp:694: undefined reference to `NdbDictionary::Column::getSizeInBytes() const'
/opt/sizer-0.30/src/sizer.cpp:694: undefined reference to `NdbDictionary::Column::getName() const'
/opt/sizer-0.30/src/sizer.cpp:703: undefined reference to `NdbDictionary::Column::getName() const'
/opt/sizer-0.30/src/sizer.cpp:744: undefined reference to `NdbDictionary::Column::getSizeInBytes() const'
sizer.o: In function `calculate_dm(Ndb*, NdbDictionary::Table const*, NdbDictionary::Index const*, int&, int&, bool, int&, bool, bool&)':
/opt/sizer-0.30/src/sizer.cpp:491: undefined reference to `NdbDictionary::Table::getNoOfColumns() const'
/opt/sizer-0.30/src/sizer.cpp:508: undefined reference to `NdbDictionary::Table::getColumn(int) const'
/opt/sizer-0.30/src/sizer.cpp:511: undefined reference to `NdbDictionary::Column::getType() const'
/opt/sizer-0.30/src/sizer.cpp:520: undefined reference to `NdbDictionary::Column::getPrimaryKey() const'
/opt/sizer-0.30/src/sizer.cpp:587: undefined reference to `NdbDictionary::Column::getStorageType() const'
/opt/sizer-0.30/src/sizer.cpp:590: undefined reference to `NdbDictionary::Column::getSizeInBytes() const'
/opt/sizer-0.30/src/sizer.cpp:598: undefined reference to `NdbDictionary::Column::getNullable() const'
/opt/sizer-0.30/src/sizer.cpp:539: undefined reference to `NdbDictionary::Column::getSizeInBytes() const'
/opt/sizer-0.30/src/sizer.cpp:540: undefined reference to `NdbDictionary::Column::getStorageType() const'
/opt/sizer-0.30/src/sizer.cpp:588: undefined reference to `NdbDictionary::Column::getSizeInBytes() const'
/opt/sizer-0.30/src/sizer.cpp:553: undefined reference to `NdbDictionary::Column::getStorageType() const'
/opt/sizer-0.30/src/sizer.cpp:548: undefined reference to `NdbDictionary::Column::getLength() const'
/opt/sizer-0.30/src/sizer.cpp:567: undefined reference to `NdbDictionary::Column::getStorageType() const'
/opt/sizer-0.30/src/sizer.cpp:522: undefined reference to `NdbDictionary::Column::getName() const'
/opt/sizer-0.30/src/sizer.cpp:525: undefined reference to `NdbDictionary::Column::getName() const'
/opt/sizer-0.30/src/sizer.cpp:516: undefined reference to `NdbDictionary::Column::getNullable() const'
/opt/sizer-0.30/src/sizer.cpp:516: undefined reference to `NdbDictionary::Column::getStorageType() const'
/opt/sizer-0.30/src/sizer.cpp:516: undefined reference to `NdbDictionary::Column::getSizeInBytes() const'
/opt/sizer-0.30/src/sizer.cpp:516: undefined reference to `NdbDictionary::Column::getName() const'
/opt/sizer-0.30/src/sizer.cpp:570: undefined reference to `NdbDictionary::Column::getSizeInBytes() const'
sizer.o: In function `supersizeme(Ndb*, char*, char*, bool, bool)':
/opt/sizer-0.30/src/sizer.cpp:812: undefined reference to `Ndb::setDatabaseName(char const*)'
/opt/sizer-0.30/src/sizer.cpp:813: undefined reference to `Ndb::getDictionary() const'
/opt/sizer-0.30/src/sizer.cpp:814: undefined reference to `NdbDictionary::Dictionary::getTable(char const*) const'
/opt/sizer-0.30/src/sizer.cpp:824: undefined reference to `NdbDictionary::Table::getName() const'
/opt/sizer-0.30/src/sizer.cpp:837: undefined reference to `NdbDictionary::Dictionary::listIndexes(NdbDictionary::Dictionary::List&, NdbDictionary::Table const&) const'
/opt/sizer-0.30/src/sizer.cpp:838: undefined reference to `NdbDictionary::Table::getNoOfColumns() const'
/opt/sizer-0.30/src/sizer.cpp:852: undefined reference to `NdbDictionary::Table::getName() const'
/opt/sizer-0.30/src/sizer.cpp:852: undefined reference to `NdbDictionary::Dictionary::getIndex(char const*, char const*) const'
/opt/sizer-0.30/src/sizer.cpp:926: undefined reference to `NdbDictionary::Table::getName() const'
/opt/sizer-0.30/src/sizer.cpp:957: undefined reference to `NdbDictionary::Table::getName() const'
sizer.o: In function `list_tables(Ndb*, char*)':
/opt/sizer-0.30/src/sizer.cpp:1306: undefined reference to `Ndb::getDictionary() const'
/opt/sizer-0.30/src/sizer.cpp:1309: undefined reference to `NdbDictionary::Dictionary::listObjects(NdbDictionary::Dictionary::List&, NdbDictionary::Object::Type)'
sizer.o: In function `main':
/opt/sizer-0.30/src/sizer.cpp:300: undefined reference to `ndb_init'
/opt/sizer-0.30/src/sizer.cpp:329: undefined reference to `Ndb_cluster_connection::Ndb_cluster_connection(char const*)'
/opt/sizer-0.30/src/sizer.cpp:337: undefined reference to `Ndb_cluster_connection::connect(int, int, int)'
/opt/sizer-0.30/src/sizer.cpp:348: undefined reference to `Ndb_cluster_connection::wait_until_ready(int, int)'
/opt/sizer-0.30/src/sizer.cpp:366: undefined reference to `Ndb::Ndb(Ndb_cluster_connection*, char const*, char const*)'
/opt/sizer-0.30/src/sizer.cpp:369: undefined reference to `Ndb::init(int)'
collect2: ld returned 1 exit status
make[2]: *** [sizer] Error 1
make[2]: Leaving directory `/opt/sizer-0.30/src'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/opt/sizer-0.30'
make: *** [all] Error 2
[root@HAMC sizer-0.30]#

Through i had find the same error here : http://forums.mysql.com/read.php?25,283165,283175 ,but i dosn't get a piece of useful information.
can somebody give me some hints. Thanks.

Other message:
[root@HAMC sizer-0.30]# rpm -qa gcc
gcc-4.1.2-46.el5
[root@HAMC sizer-0.30]# rpm -qa autoconf
autoconf-2.59-12
[root@HAMC sizer-0.30]# rpm -qa automake
automake-1.9.6-2.1
[root@HAMC sizer-0.30]# rpm -qa libtool
libtool-1.5.22-6.1
[root@HAMC sizer-0.30]# echo $PATH
/usr/kerberos/sbin:/usr/kerberos/bin:/usr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin:/root/bin
[root@HAMC sizer-0.30]# mysql_config
Usage: /usr/bin/mysql_config [OPTIONS]

Hi

Reading the mysql cluster manual I found some sentences which are negating each other, they talk about Mysql cluster replication and in particular about the ndb_apply_status.

the first is:

"This table is populated only on slaves; on the master, no DataMemory is allocated to it. However, the table is populated from the
master. For this reason, this table must be replicated and any replication filtering or binary log filtering rules that prevent this prevent
replication between clusters from operating properly. For more information about potential problems arising from such filtering
rules"



the sencond is:

"The ndb_binlog_index and ndb_apply_status tables are created in the mysql database because they should not be replicated."


So I have a doubt... has the ndb_apply_status to be replicated in a Master-Slave replica within two MySQL clusters?


Thanks

Is there global buffer and session buffer for the ndbd node of mysql cluster?
I wonder how much memory does ndbd node use per one tracsaction or one connection?

Is there any formular for mysql cluster ndbd node?

Hello,

I am a little confused about the architecture of a mysql cluster. Which one is better:

- 3 nodes, 2x(data+sql), 1xmanagement
- 4 nodes, 2xdata, 2x(sql+management)

I am concerned about how to replace a data, sql or management node in case of an hardware/os failure easily and without stopping the operation.

Thank you.

Mete