MySQL Forums - NDB clusters

MySQL NDB IP Bind Issues (1 reply)

Chris Walker — Tue, 16 Dec 2025 12:55:33 +0000

Hi there,

I'm trying to set up a new MySQL NDB cluster in a cloud environment on Debian 13, and I'm getting the following error when starting my data node using ndbmtd: (IP addresses changed for privacy)

2025-11-04 18:32:43 [ndbd] INFO -- Angel connected to '1.2.3.4:1186'
2025-11-04 18:32:48 [ndbd] INFO -- Angel allocated nodeid: 3
2025-11-04 18:32:48 [ndbd] ERROR -- Could not fetch configuration/invalid configuration, error: 'The hostname this node should have according to the configuration does not match a local interface. Attempt to bind '4.5.6.7' failed with error: 99 'Cannot assign requested address''

My data node has a public (4.5.6.7) and private (10.0.0.1) IP address. I've tried everything I can think of with bind-address =10.0.0.1 parameter but I can't get past this error.

How do I tell ndbmtd to bind to the private address 10.0.0.1 to get past this error?

If I run ndbmtd --help it even reports bind-address 10.0.0.1 but seems to ignore it completely.

HELP!

NDB Cluster docker IP addresses (no replies)

Jason Prouty — Thu, 23 Oct 2025 13:20:22 +0000

I am setting up a 5 node cluster 1 mgmt 1 sql and 3 data nodes I am having issues with the ip address
I have not been able to get docker to bring up the cluster without using the 192.168.0.0/24 network
any suggestions?

this is my docker-compose on the mgmt

Networks:
cluster_lan:
driver: macvlan
driver_opts:
parent: ens19 # your LAN NIC
ipam:
config:
- subnet: 192.168.0.0/24
gateway: 192.168.0.1

volumes:
mgmd-data: {}

services:
management1:
image: container-registry.oracle.com/mysql/community-cluster:8.4
container_name: management1
command: ["ndb_mgmd", "--config-file=/etc/mysql-cluster/config.ini", "--ndb-nodeid=1", "--initial"]
restart: unless-stopped
networks:
cluster_lan:
ipv4_address: 192.168.0.2
volumes:
- ./mysql-cluster/config.ini:/etc/mysql-cluster.cnf:ro
# - ./mysql-cluster/config.ini:/etc/mysql-cluster/config.ini:ro
- mgmd-data:/var/lib/mysql-cluster

# Host-facing proxy: listens on the VM host's :1186 and forwards to 192.168.0.2:1186
mgmd-proxy:
image: alpine/socat
container_name: mgmd-proxy
network_mode: host
restart: unless-stopped
depends_on: [management1]
command: ["TCP-LISTEN:1186,reuseaddr,fork","TCP:192.168.0.2:1186"]

~

MySQL 8.4 replication issues (3 replies)

Kallol Chakraborty — Thu, 13 Feb 2025 12:52:42 +0000

Hi ,
I want to setup replication between 2 NDB Clusters V8,4 .
Primary Cluster
2 VMS are having data nodes and management nodes
2 VMs are having mysql API nodes

my.cnf:
datadir=/var/lib/mysql
socket=/var/lib/mysql/mysql.sock

log-error=/var/log/mysql/mysqld.log
pid-file=/var/lib/mysql/mysqld.pid
log-bin = /var/lib/mysql/mysql-bin.log
max-binlog-size = 500M
server-id = 2
port = 3306
ndbcluster
ndb-nodeid = 51
max_connections=10000
table_open_cache=2000
relay_log = /var/log/mysql/mysql-relay-bin
relay_log_index = /var/log/mysql/mysql-relay-bin.index
ndb-connectstring=****,****
binlog_expire_logs_seconds = 2592000
binlog-format=ROW
replicate-do-db=
binlog-do-db=

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

Secondary Cluster
1 vm containing data node, management node and API node.

my.cnf is same as above .

But while doing the replication, the bulk data replication is not happening properly , may be some of the data is getting replicated. While doing small data set, the replication is happening. Can anybody help us to know , what is the issue

How to shorten the time after data node switchover (3 replies)

XIELEI YANG — Thu, 16 Jan 2025 10:28:12 +0000

Host A, a management node, data node and SQL node. The main data node.
Host B, a management node, data node and SQL node.

Reboot host A.
Host B accessing mysql reports error ERROR 1296 (HY000): Got error 4009 'Cluster Failure' from NDBCLUSTER
Wait about 40s for normal access.

/usr/local/app/mysql-cluster/config.ini
[tcp default]
SendBufferMemory=2M
ReceiveBufferMemory=2M

[ndbd default]
NoOfReplicas=2 ## data num
DataMemory=2048M
IndexMemory=640M

LockPagesInMainMemory=1
NoOfFragmentLogFiles=300
SchedulerSpinTimer=400
SchedulerExecutionTimer=100
RealTimeScheduler=1
TimeBetweenGlobalCheckpoints=1000
TimeBetweenEpochs=200
RedoBuffer=32M
TimeBetweenLocalCheckpoints=6

MaxNoOfOrderedIndexes=512
MaxNoOfConcurrentOperations=100000

## mng
[ndb_mgmd]
NodeId=1
hostname=10.188.68.45
datadir=/usr/local/app/mysql-cluster/

[ndb_mgmd]
NodeId=2
hostname=10.188.68.46
datadir=/usr/local/app/mysql-cluster/

## data
[ndbd]
NodeId=11
hostname=10.188.68.45
datadir=/usr/local/app/mysql/data
StopOnError=0
StartPartialTimeout=1000
StartPartitionedTimeout=1000
TransactionDeadLockDetectionTimeOut=60000
[ndbd]
NodeId=12
hostname=10.188.68.46
datadir=/usr/local/app/mysql/data
StopOnError=0
StartPartialTimeout=1000
StartPartitionedTimeout=1000
TransactionDeadLockDetectionTimeOut=60000

## sql
[mysqld]
NodeId=21
hostname=10.188.68.45
[mysqld]
NodeId=22
hostname=10.188.68.46
[mysqld]

[mysqld]

MySQL NDB Cluster 8.4 - What's new (no replies)

Edwin Desouza — Wed, 30 Oct 2024 23:28:32 +0000

MySQL NDB Cluster 8.4 - What's new
- https://blogs.oracle.com/mysql/post/mysql-ndb-cluster-84-whats-new

MySQL NDB Cluster and MCM: TLS (no replies)

Edwin Desouza — Tue, 22 Oct 2024 15:21:52 +0000

MySQL NDB Cluster and MCM: TLS
- https://blogs.oracle.com/mysql/post/ndb-tls-with-mcm

MySQL NDB Cluster: Replication (no replies)

Edwin Desouza — Wed, 12 Jun 2024 23:36:45 +0000

MySQL NDB Cluster: Replication
- https://blogs.oracle.com/mysql/post/introduction-to-mysql-ndb-cluster-replication
- https://blogs.oracle.com/mysql/post/mysql-ndb-cluster-replication-singlechannel-replication
- https://blogs.oracle.com/mysql/post/mysql-ndb-cluster-replication-dualchannel-replication-for-redundancy
- https://blogs.oracle.com/mysql/post/mysql-ndb-cluster-replication-circular-replication-for-activeactive
- https://blogs.oracle.com/mysql/post/mysql-ndb-cluster-replication-circular-replication-for-activeactive-clusters

A question about epoch boundary in system-wide recovery (2 replies)

Alex Ou — Sat, 01 Jun 2024 07:41:35 +0000

Hey guys,

I have been reading this article of Frazer Clement's lately: https://messagepassing.blogspot.com/2011/12/eventual-consistency-in-mysql-cluster.html. It got an excellent description of 'epoch'. But there is one sentence I am not sure I understand: Epoch boundaries act as markers in the flow of row events generated by each node, which are then used as consistent points to recover to.

I use the following scenario to explain my confusion: suppose at some point the NDB kernel requests all the nodes to persist last second of data changes to disk; and before that request, all data changes <= epoch 100 have been persisted to disk. After the request, some nodes do the job and eventually changes in epoch 101-110 are flushed to the REDO log; but some don't, for example, because of a busy disk sub-system. Then a system-wide crash strikes.

My question is: in the following system-wide recovery, are all the nodes recovered to epoch 100 uniformly, or each node is recovered to the largest epoch in its REDO log so that some nodes are recovered to epoch 100 but others are recovered to epoch 110?

It seems Frazer Clement's statement implies the first case to me. But I need to make sure about this.

Need help to review a serializability implementation for MySQL Cluster (8 replies)

Alex Ou — Fri, 02 Jan 2026 03:03:36 +0000

Hey guys,

I've recently made some progress in the field of consistency(C in ACID). Among other things, I've developed a serializability implementation for MySQL Cluster(NDB Cluster) to test my ideas and you are invited to peer-review it for me. I believe it is the fifth one in commercial database systems after: MySQL InnoDB's 2PL, PostgreSQL's Serializable Snapshot Isolation, Google's Spanner's isolation level(I gave a proof in Appendix D of my article, the google guys
may not have known this), CockroachDB's timestamp-based serializability implementation. The aim is to solve consistent, large(usually implies
a distributed architecture) and performance-boosted OLTP application problems, which could be daunting for those who care about consistency and
serializability. This solution to the serializability problem is a 2nd-tier one, which means it doesn't require any coding. So as long as you can
manage a MySQL Cluster, you can readily deploy and test your application with it.

This on-going project is hosted @ https://github.com/creamyfish/conflict_serializability

Current evaluation(mainly in Example 16 and Theorem 4‘ in my article) indicates it should be able to provide both consistency and performance to a fairly complex(comparing with TPCC, the warehouse like benchmark) OLTP application if it is deployed in a MySQL Cluster. However I believe testing it in other applications is necessary to come to the conclusion that whether it is able to provide both consistency and performance to many, if not most OLTP applications. So you are also invited to test your application with it to help me assess it. I will try to provide service for that.

Come check it out if you are interested in consistency and serializability. Your help is highly appreciated!

Error 1064 Duplicate entry 'ndbcluster-96' for key 'tables.engine' (7 replies)

Tony Soprano — Wed, 24 Jan 2024 13:34:02 +0000

I have a production 8.0.33-cluster MySQL Cluster Community Server.
it works fine in the last 6 months until today.
There are 28 working databases in it.

Since today I can't create any table in any dbase because it show always this error:
Error 1064 Duplicate entry 'ndbcluster-96' for key 'tables.engine'

doesn't matter the db name or table name, the errori is always the same.
For sure there is no duplicate vlues cause i used a new empty database with no tables into it.

Any help please cause online i tried anything in the last 12 hrs but nothing works.
I suppose cluster is not sync or an engine problem.
I can not reinstall all by 0 it's a production server.
Waiting your help.
Willing to pay if someone wants to assist me through my share screen or anydesk.
Thanks

Error 4009 (3 replies)

Nisa Apriliyanti — Wed, 10 Jan 2024 12:34:29 +0000

Hello,

I am making a project using 8 data nodes, and 47 sql nodes. Here's the config.ini setting in ndb management server:

[MGM]
DataDir=/usr/clustergo
HostName=192.168.1.1

[DB default]
DataDir=/usr/local/mysql/cluster
NoOfReplicas=2

## MEMORY MANAGEMENT
DataMemory=200G
StringMemory=25

## TRANSACTION
MaxNoOfConcurrentTransactions=4000000
MaxNoOfConcurrentOperations=8000000

## TRANSACTION RESOURCE ALLOCATION
TransactionMemory=20G

## LOGGING AND CHECK POINTS
FragmentLogFileSize=32M
NoOfFragmentLogFiles=600
EnableRedoControl=1

## METADATA OBJECTS: it defines pool sizes for metadata objects.
MaxNoOfTables=10240
MaxNoOfOrderedIndexes=2560
MaxNoOfUniqueHashIndexes=2560
MaxNoOfAttributes=1200000
MaxNoOfTriggers=2560
MaxNoOfConcurrentSubOperations=1024

## BOOLEAN PARAMETERS
CompressedLCP=1
LockPagesInMainMemory=1
ODirect=1

## CONTROLLING TIMEOUT, INTERVALS AND DISK PAGING
TimeBetweenInactiveTransactionAbortCheck=4000
TransactionDeadlockDetectionTimeout=12000

## Buffering and logging
RedoBuffer=128M

## CONTROLLING LOG MESSAGE
LogLevelStartup=1
LogLevelShutdown=1
LogLevelCheckpoint=8
LogLevelNodeRestart=15
LogLevelConnection=8
LogLevelError=8
LogLevelCongestion=1
MemReportFrequency=30

## BACKUP CONFIG
BackupMaxWriteSize=10M
BackupDataBufferSize=26M
BackupLogBufferSize=32M
BackupReportFrequency=10

## MULTITHREADING CONFIG
AutomaticThreadConfig=1

## PARAMETER FOR SEND BUFFER MEMORY ALLOCATION

TotalSendBufferMemory=128M

##DISK DATA BUFFERING PARAMETER
DiskPageBufferEntries=100
DiskPageBufferMemory=1024M
SharedGlobalMemory=160M

## NDB CLUSTER REALTIME PERFORMANCE
SpinMethod=DatabaseMachineSpinning
SchedulerExecutionTimer=100

[DB]
HostName=192.168.1.2
LockExecuteThreadToCPU=1
LockMaintThreadsToCPU=0

[DB]
HostName=192.168.1.3
LockExecuteThreadToCPU=1
LockMaintThreadsToCPU=0
.
. ## and so on
.
[API]
NodeId=46

[API]
NodeId=47
HostName=192.168.1.30

###

And whenever there is a large request. It got error 4009, like API (sqlnode) suddenly cannot connected to DB (datanode).

Here's log from ndb_1_cluster.log (ndb management):
2024-01-05 16:50:16 [MgmtSrvr] INFO -- Node 4: Index usage is 0%(20523 32K pages of total 5735985)
2024-01-05 16:50:19 [MgmtSrvr] INFO -- Node 3: Data usage is 12%(816695 32K pages of total 6533144)
2024-01-05 16:50:19 [MgmtSrvr] INFO -- Node 3: Index usage is 0%(20456 32K pages of total 5736905)
2024-01-05 16:50:30 [MgmtSrvr] ALERT -- Node 9: Node 47 Disconnected
2024-01-05 16:50:30 [MgmtSrvr] INFO -- Node 9: Communication to Node 47 closed
2024-01-05 16:50:30 [MgmtSrvr] INFO -- Node 7: Communication to Node 47 closed
2024-01-05 16:50:30 [MgmtSrvr] INFO -- Node 3: Communication to Node 47 closed
2024-01-05 16:50:30 [MgmtSrvr] INFO -- Node 6: Communication to Node 47 closed
2024-01-05 16:50:30 [MgmtSrvr] INFO -- Node 4: Communication to Node 47 closed
2024-01-05 16:50:30 [MgmtSrvr] INFO -- Node 5: Communication to Node 47 closed
2024-01-05 16:50:30 [MgmtSrvr] INFO -- Node 2: Communication to Node 47 closed
2024-01-05 16:50:30 [MgmtSrvr] ALERT -- Node 2: Node 47 Disconnected
2024-01-05 16:50:30 [MgmtSrvr] INFO -- Node 8: Communication to Node 47 closed
2024-01-05 16:50:30 [MgmtSrvr] ALERT -- Node 6: Node 47 Disconnected
2024-01-05 16:50:30 [MgmtSrvr] ALERT -- Node 7: Node 47 Disconnected
2024-01-05 16:50:30 [MgmtSrvr] ALERT -- Node 4: Node 47 Disconnected
2024-01-05 16:50:30 [MgmtSrvr] ALERT -- Node 5: Node 47 Disconnected
2024-01-05 16:50:30 [MgmtSrvr] ALERT -- Node 8: Node 47 Disconnected
2024-01-05 16:50:30 [MgmtSrvr] ALERT -- Node 3: Node 47 Disconnected
2024-01-05 16:50:31 [MgmtSrvr] INFO -- Node 6: Data usage is 12%(821829 32K pages of total 6532706)
2024-01-05 16:50:31 [MgmtSrvr] INFO -- Node 6: Index usage is 0%(20894 32K pages of total 5731771)
2024-01-05 16:50:33 [MgmtSrvr] INFO -- Node 6: Communication to Node 47 opened
2024-01-05 16:50:33 [MgmtSrvr] INFO -- Node 3: Communication to Node 47 opened
2024-01-05 16:50:33 [MgmtSrvr] INFO -- Node 8: Communication to Node 47 opened
2024-01-05 16:50:33 [MgmtSrvr] INFO -- Node 5: Communication to Node 47 opened
2024-01-05 16:50:33 [MgmtSrvr] INFO -- Node 9: Communication to Node 47 opened
2024-01-05 16:50:33 [MgmtSrvr] INFO -- Node 7: Communication to Node 47 opened
2024-01-05 16:50:33 [MgmtSrvr] INFO -- Node 2: Communication to Node 47 opened
2024-01-05 16:50:34 [MgmtSrvr] INFO -- Node 4: Communication to Node 47 opened
2024-01-05 16:50:34 [MgmtSrvr] INFO -- Node 9: Node 47 Connected
2024-01-05 16:50:34 [MgmtSrvr] INFO -- Node 6: Node 47 Connected
2024-01-05 16:50:34 [MgmtSrvr] INFO -- Node 8: Node 47 Connected
2024-01-05 16:50:34 [MgmtSrvr] INFO -- Node 9: Node 47: API mysql-8.0.35 ndb-8.0.35
2024-01-05 16:50:34 [MgmtSrvr] INFO -- Node 8: Node 47: API mysql-8.0.35 ndb-8.0.35
2024-01-05 16:50:34 [MgmtSrvr] INFO -- Node 6: Node 47: API mysql-8.0.35 ndb-8.0.35
2024-01-05 16:50:34 [MgmtSrvr] INFO -- Node 2: Node 47 Connected
2024-01-05 16:50:34 [MgmtSrvr] INFO -- Node 7: Node 47 Connected
2024-01-05 16:50:34 [MgmtSrvr] INFO -- Node 7: Node 47: API mysql-8.0.35 ndb-8.0.35
2024-01-05 16:50:34 [MgmtSrvr] INFO -- Node 2: Node 47: API mysql-8.0.35 ndb-8.0.35
2024-01-05 16:50:35 [MgmtSrvr] INFO -- Node 3: Node 47 Connected
2024-01-05 16:50:35 [MgmtSrvr] INFO -- Node 4: Node 47 Connected
2024-01-05 16:50:35 [MgmtSrvr] INFO -- Node 5: Node 47 Connected
2024-01-05 16:50:35 [MgmtSrvr] INFO -- Node 4: Node 47: API mysql-8.0.35 ndb-8.0.35
2024-01-05 16:50:35 [MgmtSrvr] INFO -- Node 3: Node 47: API mysql-8.0.35 ndb-8.0.35
2024-01-05 16:50:35 [MgmtSrvr] INFO -- Node 5: Node 47: API mysql-8.0.35 ndb-8.0.35

So my guess there is something wrong with the connection between api and db.
Although they are in the same block IP, and there is no firewall set-up in between.
I have checked that Ubuntu 20 do not have SELinux, and UFW status is inactive. I also do not set-up any IP tables.

and for the apps, we are using web application, which although in different block IP (192.168.2.xx), It able to ping under 1ms. there is no firewall, SElinux, ufw, or iptables as well.

but still for a long query it can takes 4 sec to 4 minutes to complete if the traffic is not that much crowded.

If it is in high time access, users often found error 4009, which makes another error code 1296, 1297, or even mysql has gone away.
I have been working on this for 2 days, and I can't find the cause.
please help, thank you.

MySQL Cluster (NDB) spread data (rows) to 4 data-nodes servers (1 reply)

Ali Saeidi — Tue, 05 Dec 2023 19:19:08 +0000

I want to spread my MySQL rows to 4 servers (Horizontal sharding). I searched, and I found that I have to use NDB cluster (MySQL cluster). I made a MySQL server/client with NDB manager server and 4 data nodes servers and this is my manager configuration :

[ndbd default]
NoOfReplicas=1

[ndb_mgmd]
NodeId=1
hostname=192.168.159.133
datadir=/var/lib/mysql-cluster

[ndbd]
NodeId=2
hostname=192.168.159.131
datadir=/home/db

[ndbd]
NodeId=3
hostname=192.168.159.132
datadir=/home/db

[ndbd]
NodeId=4
hostname=192.168.159.137
datadir=/home/db

[mysqld]
NodeId=20
hostname=192.168.159.133

I know replication means make a backup of each row to another server and I don't want it (I just want to spread my data (rows) to 4 servers, not making backup) so I set NoOfReplicas to 1 to have 4 nodegroups ...

Am I right ? Does my data (rows) spread on that 4 data-node servers ?

If I right, what is different between doing this, or just using Innodb and make foreign partitions (on remote servers) ? Because it's a lot easier to make partition (key) by my own and attach each partition to remote servers !!!

Is using NDB has more advantage (about what I want to do (spread data, not replication (making backup))) ?

And final question, is it right to have NDBCLUSTER table with also own partitions ???!!! What is that mean, anyway ? For example, I have 4 data-nodes and for a NDBCLUSTER table, I create 8 partitions too (key partition) ! How that's work? Does it create 8 partitions on each data-node ? Or just split those partitions on those 4 data-nodes server (for example, each data-node holds 2 partitions) ?

Error while trying ndb_restore (6 replies)

Nisa Apriliyanti — Wed, 29 Nov 2023 08:57:37 +0000

Hello,
I am a student and still unfamilliar with mysql cluster. I am trying to do backup and restore.

1. I have config in config.ini for back up as followed:

## BackUp setting
## BackupDataDir automatically follow DataDir /home/user/BACKUP
BackupLogBufferSize=16M
BackupReportFrequency=10

2. This is the cluster that has been configured.

ndb_mgm> show
Cluster Configuration
---------------------
[ndbd(NDB)] 2 node(s)
id=2 @192.168.1.236 (mysql-8.0.35 ndb-8.0.35, Nodegroup: 0, *)
id=3 @192.168.1.237 (mysql-8.0.35 ndb-8.0.35, Nodegroup: 0)

[ndb_mgmd(MGM)] 1 node(s)
id=1 @192.168.1.238 (mysql-8.0.35 ndb-8.0.35)

[mysqld(API)] 3 node(s)
id=10 @192.168.1.239 (mysql-8.0.35 ndb-8.0.35)
id=11 @192.168.1.240 (mysql-8.0.35 ndb-8.0.35)
id=12 @192.168.1.243 (mysql-8.0.35 ndb-8.0.35)

3. I have done backup at ndb_mgm

ndb_mgm > start backup
Connected to Management Server at: localhost:1186
Waiting for completed, this may take several minutes
Node 3: Backup 1 started from node 1
Node 2: Local backup status: backup 1 started from node 1
#Records: 14001933 #LogRecords: 243288
Data: 832059592 bytes Log: 21435756 bytes
.
.
.
Node 3: Backup 1 started from node 1 completed
StartGCP: 201318 StopGCP: 201401
#Records: 28027692 #LogRecords: 656042
Data: 1665876984 bytes Log: 55078372 bytes

4. then, I try deleting some tables.

5. after that, I want to try restoring it. However there are some error, that I can't find the solution.

######First error when I shutdown ndb cluster, then only activate ndb_mgmd.

datanode236:/home/user/# ndb_restore -n 2 -b 1 -m --ndb-connectstring=192.168.1.238:1186 --ndb-nodeid=1 --backup-path=BACKUP/BACKUP-1
Nodeid = 2
Backup Id = 1
backup path = BACKUP/BACKUP-1
2023-11-28 08:37:48 [NdbApi] INFO -- Configuration error: Error: Could not alloc node id at 192.168.1.238:1186: Id 1 configured as ndb_mgmd(MGM), connect attempted as mysqld(API).
Could not connect to cluster: '1 - Configuration error: Error: Could not alloc node id at 192.168.1.238:1186: Id 1 configured as ndb_mgmd(MGM), connect attempted as mysqld(API).'

########Second Error when ndb cluster all running. At datanode 192.168.1.236:

datanode236:/home/user/#ndb_restore -n 2 -b 1 -m --ndb-connectstring=192.168.1.238:1186 --backup-path=BACKUP/BACKUP-1
Nodeid = 2
Backup Id = 1
backup path = BACKUP/BACKUP-1
2023-11-28 08:38:06 [NdbApi] INFO -- Configuration error: Error: Could not alloc node id at 192.168.1.238:1186: Connection done from wrong host ip 192.168.1.236.
Could not connect to cluster: '1 - Configuration error: Error: Could not alloc node id at 192.168.1.238:1186: Connection done from wrong host ip 192.168.1.236.'

Please help if you know what I miss.
Thank you.

NBBCluster not sync autoincrement values between mysql server nodes (2 replies)

Tony Soprano — Sun, 17 Sep 2023 14:24:55 +0000

I have a NDBcluster on 2 physical servers with this layout:
vm1 ndb manager + mysql server #1
vm2 mysql server #2
vm3 data node #1
vm4 data node #2

i import many dbase on vm1 using mysql commnand line.
i can see and access all data from both vm1 and vm2.
but after 2 months of perfect usage,
vm2 mysql server if i insert data in any table of any dbase start to use
weird and not syncronized value for autoincrement of any id primary key.

example:
on vm1: insert into user (name,email) values ("tony","t@t.com")
insert into user (name,email) values ("john","f@f.com")
result on both vm1 and vm2:
id=8 , name=tony, email=t@t.com
id=9 , name=john, email=f@f.com

then i do on vm2:
insert into user (name,email) values ("kris","k@k.com")
result on both vm1 and vm2:
id=8 , name=tony, email=t@t.com
id=9 , name=john, email=f@f.com
id=521 , name=kris, email=k@k.com

Can someone explain me why this happen? why after 2 months and how to fix this please!

XA transaction causes Mysql crash in 8.0.34 (no replies)

Raul Andres — Wed, 16 Aug 2023 08:14:50 +0000

I have the following snippet:

# cat xacrash.sql
drop database if exists newdb;
create database newdb;
use newdb;
create table innodbtable(id int) engine=innodb;
xa begin 'innodbtx';
insert into innodbtable values(3);
xa end 'innodbtx';
xa prepare 'innodbtx';
xa commit 'innodbtx';
create table ndbtable(id int) engine=ndbcluster;
xa begin 'ndbtx';
insert into ndbtable values(3);
xa end 'ndbtx';
xa prepare 'ndbtx';
xa commit 'ndbtx';

When running against 8.0.28 works without problems, but crashes connection in 8.0.34

--------------
xa prepare 'ndbtx'
--------------

ERROR 2013 (HY000) at line 14: Lost connection to MySQL server during query

And writes a crash report

Aug 16 10:08:54 hostname mysqld[606104]: 2023-08-16T08:08:54Z UTC - mysqld got signal 11 ;
Aug 16 10:08:54 hostname mysqld[606104]: Most likely, you have hit a bug, but this error can also be caused by malfunctioning hardware.
Aug 16 10:08:54 hostname mysqld[606104]: BuildID[sha1]=a570f2d544031bf853200e0bb758215b0b317fb1
Aug 16 10:08:54 hostname mysqld[606104]: Thread pointer: 0x7fa758000fe0
Aug 16 10:08:54 hostname mysqld[606104]: Attempting backtrace. You can use the following information to find out
Aug 16 10:08:54 hostname mysqld[606104]: where mysqld died. If you see no messages after this, something went
Aug 16 10:08:54 hostname mysqld[606104]: terribly wrong...
Aug 16 10:08:54 hostname mysqld[606104]: stack_bottom = 7fa7b42edc10 thread_stack 0x100000
Aug 16 10:08:54 hostname mysqld[606104]: /usr/sbin/mysqld(my_print_stacktrace(unsigned char const*, unsigned long)+0x41) [0x2131091]
Aug 16 10:08:54 hostname mysqld[606104]: /usr/sbin/mysqld(print_fatal_signal(int)+0x2a2) [0xfee7d2]
Aug 16 10:08:54 hostname mysqld[606104]: /usr/sbin/mysqld(handle_fatal_signal+0xa5) [0xfee985]
Aug 16 10:08:54 hostname mysqld[606104]: /lib64/libpthread.so.0(+0x12cf0) [0x7fa7dcabbcf0]
Aug 16 10:08:54 hostname mysqld[606104]: Trying to get some variables.
Aug 16 10:08:54 hostname mysqld[606104]: Some pointers may be invalid and cause the dump to abort.
Aug 16 10:08:54 hostname mysqld[606104]: Query (7fa7581af9c0): xa prepare 'ndbtx'
Aug 16 10:08:54 hostname mysqld[606104]: Connection ID (thread ID): 14
Aug 16 10:08:54 hostname mysqld[606104]: Status: NOT_KILLED
Aug 16 10:08:54 hostname mysqld[606104]: The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains
Aug 16 10:08:54 hostname mysqld[606104]: information that should help you find out what is causing the crash.

# rpm -qi mysql-cluster-community-server
Name : mysql-cluster-community-server
Version : 8.0.34
Release : 1.el8
Architecture: x86_64

Mysql NDB Cluster error while restoration of data "ERROR 1114 (HY000) at line 25: The table 'table1' is full" (1 reply)

purval patel — Tue, 02 May 2023 13:48:06 +0000

I have created mysql NDB Cluster with two data nodes and two mysql servers.
below is the configuration of ndb_mgmd.

$cat /usr/mysql-cluster/config.ini
[ndbd default]
NoOfReplicas=2
DataMemory=1024M
IndexMemory=54M
MaxNoOfConcurrentOperations=100000
MaxNoOfLocalOperations=110000
MaxNoOfTables=4096
MaxNoOfTriggers=3500
MaxNoOfAttributes=25000

[ndb_mgmd]
hostname=172.31.16.19
datadir=/usr/mysql-cluster
NodeId=1

[ndbd]
hostname=172.31.20.59
NodeId=11
datadir=/usr/local/mysql/data

[ndbd]
hostname=172.31.16.136
NodeId=12
datadir=/usr/local/mysql/data

[mysqld]
hostname=172.31.16.136
NodeId=21

[mysqld]
hostname=172.31.20.59
NodeId=22

When i am trying to restore the databackup .sql file. which is around 2.2 GB in size at that time i am getting error of table is full.
i have checked the disk storage but it is showing available.
Please suggest, i am stuck with the issue from last two days.

need to add new ndb data node to my cluster (1 reply)

Tony Tawk — Fri, 10 Mar 2023 10:53:37 +0000

Dear,
we have ndb cluster 7.4.10 with mysql version is 5.6.28 ndb-7.4.10
we have 2 data nodes with replica 2.
can we add another third node to this cluster?

why when we start the two nodes the commands hungs. for example when i try to use use DB1 it hangs
why it is hungging?

please, advise.

Error with Indexes (1 reply)

Jeff Steele — Sat, 25 Feb 2023 20:04:04 +0000

I added to more nodes to my cluster. I put them in a separate node group and everything ran fine for a week. Then I noticed that the new nodes didn't have much data so I ran the alter table command to redistribute the data. During that, the cluster crashed. I could not restart it and was forced to restore from backup. Now, however, I get this error:

| xxxx | analyze | Error | Got error 4721 'Mysqld: index stats thread not open for requests' from NDB |
| xxxx | analyze | Warning | index stats (RPK) for key vote_id: unexpected error 4721 |
| xxxx | analyze | Warning | index stats (RPK) for key vote_id: unexpected error 4721 |
| xxxx | analyze | status | Operation failed

Everything is working very slowly so I assume that indexes are not being used. I did not import indexes the data restoration, but did run the rebuild command separately. Does anyone have any idea what to do about this problem?

How to restart or recover data when all data nodes crash and then fail to complete start up due to frag log error in phase 4 (1 reply)

Rowan Drew — Sat, 18 Feb 2023 07:20:33 +0000

We've been running an older version of MySQL Cluster 7.4.7 for many years with minimum configuration, containing 2 data nodes, 2 sql nodes, and 1 management node.
After running an Alter Table statement to add 2 big integer columns to a table with 1,000,000 rows. the query failed and crashed the 1st data node. Upon running the query again it crashed the 2nd data node, bringing down the whole cluster.
When trying to restart either data node, they both fail during start up calling in phase 4 when reaching a frag file. see error below in logs.

So the question is, is it possible to repair or have the data nodes ignore the frag file(s) that's stopping the start up process from completing? Or how do you get around this "File has already been opened" error? We tried moving the problematic S11.FragLog file but then errors get reported that a file is missing.
If there is no way to fix these broken frag files, is there a way to recover the table data from a data node (such as using a separate tool to read/export the node's data stored on disk)?
A more general question is how do you recover data when all data nodes in a cluster cannot start (say due a single corrupt file) and there's no separate backups available?

$./ndbmtd
...
2023-02-11 06:05:13 [ndbd] INFO -- LDM instance 0: Restored T1474F1 LCP 0 rows, 1 millis, 0 rows/s)
2023-02-11 06:05:13 [ndbd] INFO -- LDM instance 0: Restored T1477F0 LCP 161953 rows, 622 millis, 260374 rows/s)
2023-02-11 06:05:14 [ndbd] INFO -- LDM instance 0: Restored T1477F1 LCP 163565 rows, 630 millis, 259626 rows/s)
2023-02-11 06:05:14 [ndbd] INFO -- LDM instance 0: Restored T1482F0 LCP 1 rows, 1 millis, 1000 rows/s)
2023-02-11 06:05:14 [ndbd] INFO -- LDM instance 0: Restored T1482F1 LCP 3 rows, 1 millis, 3000 rows/s)
2023-02-11 06:05:14 [ndbd] INFO -- LDM instance 0: Restored LCP : 1114 fragments, 47359940 rows, 160001 millis, 295997 rows/s
2023-02-11 06:05:14 [ndbd] INFO -- LDM(0): Completed fuzzy restore 1118 fragments (1118 from LCP, 0 by non-trans copy)
2023-02-11 06:05:14 [ndbd] INFO -- LDM(0): Starting DD Undo log application
2023-02-11 06:05:14 [ndbd] INFO -- LDM(0): Completed DD Undo log application
2023-02-11 06:05:14 [ndbd] INFO -- LDM(0): Starting REDO log execution phase 0
2023-02-11 06:05:14 [ndbd] INFO -- LDM(0): Node 3 ready to execute REDO log
2023-02-11 06:05:14 [ndbd] INFO -- LDM(0): All starting nodes ready to execute REDO log. Phases completed = 0
2023-02-11 06:05:14 [ndbd] INFO -- LDM(0):Ready to start execute REDO log phase, collect REDO log execution info phase completed
2023-02-11 06:05:14 [ndbd] INFO -- LDM(0): Log part 0 will execute REDO log records from GCI 85012871 -> 85013314 and last log file is number 11 and last MByte in this file is 13
2023-02-11 06:05:14 [ndbd] INFO -- LDM(0): Log part 1 will execute REDO log records from GCI 85012871 -> 85013314 and last log file is number 2 and last MByte in this file is 12
2023-02-11 06:05:14 [ndbd] INFO -- LDM(0): Log part 2 will execute REDO log records from GCI 85012871 -> 85013314 and last log file is number 6 and last MByte in this file is 6
2023-02-11 06:05:14 [ndbd] INFO -- LDM(0): Log part 3 will execute REDO log records from GCI 85012871 -> 85013314 and last log file is number 11 and last MByte in this file is 14
2023-02-11 06:05:14 [ndbd] INFO -- LDM(0): Start executing REDO log for part 0
2023-02-11 06:05:14 [ndbd] INFO -- LDM(0): Start executing REDO log for part 1
2023-02-11 06:05:14 [ndbd] INFO -- LDM(0): Start executing REDO log for part 2
2023-02-11 06:05:14 [ndbd] INFO -- LDM(0): Start executing REDO log for part 3
2023-02-11 06:05:14 [ndbd] INFO -- LDM(0): Completed REDO log execution on part 1, ops executed = 0, bytes executed = 0,
2023-02-11 06:05:14 [ndbd] INFO -- LDM(0): Log part 1 stats: ops skipped = 735, ops prepared 735, pages read = 8, GCIs executed = 444
2023-02-11 06:05:14 [ndbd] INFO -- LDM(0): Completed REDO log execution on part 0, ops executed = 388, bytes executed = 7212,
2023-02-11 06:05:14 [ndbd] INFO -- LDM(0): Log part 0 stats: ops skipped = 639, ops prepared 1027, pages read = 8, GCIs executed = 1283
2023-02-11 06:05:14 [ndbd] INFO -- LDM(0): Completed REDO log execution on part 2, ops executed = 249, bytes executed = 49328,
2023-02-11 06:05:14 [ndbd] INFO -- LDM(0): Log part 2 stats: ops skipped = 7320, ops prepared 7569, pages read = 48, GCIs executed = 2080
2023-02-11 06:05:15 [ndbd] INFO -- open: >/var/lib/mysql-cluster/data/ndb_3_fs/D11/DBLQH/S11.FragLog< existing: >/var/lib/mysql-cluster/data/ndb_3_fs/D11/DBLQH/S11.FragLog<
2023-02-11 06:05:15 [ndbd] INFO -- OpenFiles::insert()
2023-02-11 06:05:15 [ndbd] INFO -- Error handler shutting down system
2023-02-11 06:05:15 [ndbd] INFO -- Error handler shutdown completed - exiting
2023-02-11 06:05:18 [ndbd] ALERT -- Node 3: Forced node shutdown completed. Occured during startphase 4. Caused by error 2807: 'File has already been opened(Internal error, programming error or missing error message, please report a bug). Temporary error, restart node'.

NDB: stored grants: not intialized. (1 reply)

Ricky Bobby — Wed, 04 Jan 2023 15:55:10 +0000

Attempting to get my first cluster going and adding users ran into this message.

NDB: stored grants: not intialized.

I followed these instructions:
https://dev.mysql.com/doc/mysql-cluster-excerpt/8.0/en/mysql-cluster-privilege-synchronization.html

This is in a kubernetes environment and deployed with a bash script on boot. I have "sleep 5" after the server starts and forks away, This is in a file:

GRANT NDB_STORED_USER ON *.* TO `root`@`localhost`

FLUSH PRIVILEGES;

CREATE USER IF NOT EXISTS 'ndb_demo'@'%' IDENTIFIED BY 'suuuuperseeeecret';

Then I get the error and I'm not finding any documentation that explains it.

Should I sleep longer to let the sql server join the cluster?

NDB 8.0 Example Doesn't Work (1 reply)

Ricky Bobby — Wed, 04 Jan 2023 15:13:05 +0000

I'm trying to follow this tutorial: https://dev.mysql.com/doc/refman/8.0/en/mysql-cluster-config-starting.html

Attempting to start the second management node always dies. The first node rejects the second.

#First node started logs this: Refusing other node, it has different checksum: 0x24d61568, expected: 0x25d62474

#Second node started logs this:-- Got CONFIG_CHECK_REF from node 1, error: 3, message: 'Wrong checksum', generation: 0, expected generation: 0, state: 1, expected state: 1 own-state: 1

I copy and pasted the config and ONLY changed the host names and NodeId.

It doesn't help if I start with --initial on one or both nodes. Thoughts?

MySQL NDB Cluster 8.0.31 Transparent Data Encryption (no replies)

Edwin Desouza — Thu, 22 Dec 2022 21:39:24 +0000

MySQL NDB Cluster 8.0.31 Transparent Data Encryption
- https://blogs.oracle.com/mysql/post/mysql-cluster-8031-transparent-data-encryption

RH/Oracle Linux 9 Yum Repo Empty (2 replies)

Jeff Steele — Fri, 02 Dec 2022 23:57:09 +0000

I am going to add two more data nodes to my cluster and am in the process of setting up new servers. I am planning to use Oracle Linux 9. However, the yum repository for that version doesn't have any RPMs in it:

http://repo.mysql.com/yum/mysql-cluster-8.0-community/el/9/x86_64/

Does anyone know if this is only temporary or will RPMs eventually be there? I normally use yum to keep my systems up to date.

Thanks!

About High availability (2 replies)

domenico pandolfino — Tue, 29 Nov 2022 09:56:20 +0000

Hi all, i've installed mysql cluster via deb and apt.
i followed this guide: https://dev.mysql.com/doc/mysql-apt-repo-quick-guide/en/#repo-qg-apt-cluster-install
-----------------------------------------------------
i want to have 2 VM running management and SQL together
and 2 VM for data node on.

So it's possible to have mysqld and ndb_mgmd running on same VM x 2?
i've tried but it's not working.
----------------------------------------------------------
here my /etc/my.cnf on VM1 and VM2:
[mysqld]
ndbcluster

[mysql_cluster]
ndb-connectstring=dbmng1,dbmng2
-----------------------------------------------------------
here my config.ini on VM1 and VM2:
[ndbd default]
NoOfReplicas=2
DataMemory=98M

[ndb_mgmd]
NodeId=1
HostName=dbmng1
DataDir=/var/lib/mysql-cluster

[ndb_mgmd]
NodeId=2
HostName=dbmng2
DataDir=/var/lib/mysql-cluster

[ndbd]
NodeId=3
HostName=dbdata1
DataDir=/usr/local/mysql/data

[ndbd]
NodeId=4
HostName=dbdata2
DataDir=/usr/local/mysql/data

[mysqld]
HostName=dbmng1

[mysqld]
HostName=dbmng2
--------------------------------------------------

Node2 & Node3 Cluster requires this node to be started with --initial (2 replies)

Richard InTx — Sat, 05 Nov 2022 17:26:56 +0000

Hi all newbie here (well less than a newbie, idiot).

I have a 3 node MySQL cluster that was installed via Docker (MySQL Docker Image 7.5.10-1.1.5), which this deployment was created by someone that isn't available to me anymore. The DB is used for Grafana and each of the Grafana's are operational and the 3 Nodes Grafana DBs are in sync.

The problem is on Node2 (Zoo2) and Node3 (Zoo3) the NDBD keeps restarting. I am pretty sure the logging is telling me what do to with the "Cluster requires this node to be started with --initial" log entry. Though I can figure out what that really means or how to start the docker cluster node with "--initial"... because I am to stupid to figure it out with all the reading I have found on the internet about Docker/MySQL.

I do a apologize for coming in here with "Hat in Hand" and not being able to understand this MySQL Cluster setup myself. I hope not to be flamed to hard and someone will have pity on me.

{"log":"2022-11-05 13:41:43 [ndbd] INFO -- NDB start phase 1 completed\n","stream":"stdout","time":"2022-11-05T13:41:43.252099351Z"}
{"log":"2022-11-05 13:41:43 [ndbd] INFO -- Start phase 2 completed\n","stream":"stdout","time":"2022-11-05T13:41:43.252102151Z"}
{"log":"2022-11-05 13:41:43 [ndbd] INFO -- Phase 2 did more initialisations, master accepted our start, we started REDO log initialisations\n","stream":"stdout","time":"2022-11-05T13:41:43.252104554Z"}
{"log":"2022-11-05 13:41:43 [ndbd] INFO -- Start NDB start phase 2\n","stream":"stdout","time":"2022-11-05T13:41:43.252108664Z"}
{"log":"2022-11-05 13:41:43 [ndbd] INFO -- Request permission to start our node from master Starting\n","stream":"stdout","time":"2022-11-05T13:41:43.275526623Z"}
{"log":"2022-11-05 13:41:43 [ndbd] INFO -- Cluster requires this node to be started with --initial as partial start has been performed and this filesystem is unusable\n","stream":"stdout","time":"2022-11-05T13:41:43.282072895Z"}
{"log":"2022-11-05 13:41:43 [ndbd] INFO -- DBDIH (Line: 2267) 0x00000002\n","stream":"stdout","time":"2022-11-05T13:41:43.282083458Z"}
{"log":"2022-11-05 13:41:43 [ndbd] INFO -- Error handler shutting down system\n","stream":"stdout","time":"2022-11-05T13:41:43.282094445Z"}
{"log":"2022-11-05 13:41:43 [ndbd] INFO -- Error handler shutdown completed - exiting\n","stream":"stdout","time":"2022-11-05T13:41:43.320431813Z"}
{"log":"2022-11-05 13:41:43 [ndbd] ALERT -- Node 5: Forced node shutdown completed. Occured during startphase 3. Caused by error 2311: 'Conflict when selecting restart type(Internal error, programming error or missing error message, please report a bug). Temporary error, restart node'.\n","stream":"stdout","time":"2022-11-05T13:41:43.375021266Z"}

f13e0be154f557317a34c6267b0a0847247aa4073775e7f3d46a3720da4b2043 10.46.133.180:5000/mysql/mysql-cluster "/entrypoint.sh mysqld --ndb-nodeid=8" 2 months ago Up 2 hours (healthy) mysqlcluster_mysql2_1
d80a9e1a859d01e3812c40d7802edeba62842906eed91c858c74f95a6d55bca3 10.46.133.180:5000/mysql/mysql-cluster "/entrypoint.sh ndbd --ndb-nodeid=5 --nowait-nodes=5,6" 2 months ago Up 40 seconds (health: starting) mysqlcluster_ndb2_1
724caf3849d69a72c135065c424a06813cff8e565f3dbe7054a91febe7dc08a7 10.46.133.180:5000/mysql/mysql-cluster "/entrypoint.sh ndb_mgmd --ndb-nodeid=2" 2 months ago Up 2 hours (unhealthy) mysqlcluster_management2_1

Insert large longtest failed on NDB (3 replies)

Eric Poon — Fri, 04 Nov 2022 22:18:46 +0000

Hello Everyone,

We want to use longtext column to save big data for an application. I got the error below when trying to insert a 500M string into a longtext column on a NDB. The same insert can be done on a SQL node as a standalone InnoDB.

I checked the documents, default value of MaxDMLOperationsPerTransaction is already maximum 4294967295. The NDB is isolated and should not have concurrent operations. I don't know what we can do.

Anyone please help.

Error:
Error Code: 1296. Got error 261 'DML count in transaction exceeds config parameter MaxDMLOperationsPerTransaction/MaxNoOfConcurrentOp' from NDBCLUSTER

Table:
CREATE TABLE `big_data_test` (
`id` int NOT NULL AUTO_INCREMENT,
`val` longtext,
`record_id` int DEFAULT NULL,
PRIMARY KEY (`id`)
) ENGINE=ndbcluster AUTO_INCREMENT=5 DEFAULT CHARSET=ascii;

SQL:
INSERT INTO big_data_test (val, record_id)
VALUES (REPEAT('x',1024*1024*500),3);

NDB:
1 management node 2G RAM
2 data nodes 6G RAM
1 SQL node 4G RAM

[ndbd default]
NoOfReplicas=1
DataMemory=1G
SharedGlobalMemory=1G
FragmentLogFileSize=64M
TimeBetweenLocalCheckpoints=12

How to build NDB clusters from source code in arm ubuntu (1 reply)

wei wu — Mon, 22 Aug 2022 08:01:30 +0000

How to build NDB clusters from source code in arm ubuntu, or how to get arm NDB clusters

MySQL Cluster 8 - 4 nodes (1 reply)

Chris Murrell — Wed, 04 Jan 2023 13:32:49 +0000

Hello.

So we are running 4 nodes and 2 masters

the same exact as this

https://www.mysql.com/products/cluster/availability.html

But if 2 of my nodes lose connection or go down they wont auto reconnect i have tried a few different things, and if i just restart them manually they crash the entire cluster.

and if i restart the remaing 2 nodes they wont start because it says not enough nodes to start...

note: im saying if an A from group 0 and B from group 1 goes down so its still actually running so that the partitions are still accessable

I am not sure in what world this is HA.

Is there a fix for this?

- (no replies)

Thomas Spray — Tue, 21 Jun 2022 12:36:12 +0000

Mysql NDB cluster - Big import fail (11 replies)

Cesar Hernandez — Wed, 08 Jun 2022 06:29:05 +0000

Hi

I'm having some issues trying to import a big (12 GB) mysql dump. The dump is from an internal mysql database (no ndb) and I'm trying to insert it to a new mysql ndb cluster (changed all sentences ENGINE=INNODB to ENGINE=NDBCLUSTER).

I've had different issues, some of the errors trying to import were fixed changing configuration parameters, but some others don't. In fact, almost the configuration parameters have been changed as a consequence of an error fired.
For example, the last one that (randomly) appears is:

ERROR 1297 (HY000) at line 9831: Got temporary error 4010 'Node failure caused abort of transaction' from NDBCLUSTER
Warning (Code 1297): Got temporary error 4010 'Node failure caused abort of transaction' from NDB
Error (Code 1297): Got temporary error 4010 'Node failure caused abort of transaction' from NDBCLUSTER
Error (Code 1180): Got error 4010 - 'Unknown error 4010' during COMMIT

Every time an error is fired seems is not related to out of ram, out of disk, or other operating system related issues.

It seems to my that this ndb cluster is too hard to configure, compared to a simple mysql database (no configuration at all and it simply works).

Is there any standard configuration that may fit for this "big" environments? (and I said "big" because my database dump is 12 GB which is not too big).
Or is there any configuration parameters related to these mysql import problems?

This dump can be inserted without issues on a mysql database (no cluster)

My environment is:

- one management node (16 GB RAM)

- two ndb nodes (32 GB RAM each)

- one mysql server node (16 GB RAM)

All mysql cluster versions software are 8.0.29.

config.ini:

[ndbd default]
# Options affecting ndbd processes on all data nodes:
NoOfReplicas=2

#MaxNoOfConcurrentOperations must be greater than MaxNoOfConcurrentTransactions
MaxNoOfConcurrentOperations = 1629496
MaxNoOfConcurrentTransactions = 1629496
MaxDMLOperationsPerTransaction = 1629400
#MaxNoOfConcurrentOperations = 4294967039
#MaxNoOfConcurrentTransactions = 4294900000
#MaxDMLOperationsPerTransaction = 4294967295

DataMemory = 16000M # Memory allocate for data storage
IndexMemory = 2048M # Memory allocate for index storage

#temporal para import inicial
NoOfFragmentLogFiles = 1000

SharedGlobalMemory = 10G

MaxNoOfOrderedIndexes = 1000
MaxNoOfAttributes = 100000

TransactionDeadlockDetectionTimeout = 10000

#para evitar REDO log files overloaded error
TimeBetweenLocalCheckpoints = 2

FragmentLogFileSize = 32M

[tcp default]
#hay un error de Out of SendBufferMemory in sendSignal
SendBufferMemory=16M
ReceiveBufferMemory=16M

[ndb_mgmd]
# Management process options:
hostname=wocu-ha-mysqlcluster-dev-1 # Hostname of the manager
datadir=/var/lib/mysql-cluster # Directory for the log files

[ndbd]
hostname=wocu-ha-mysqlcluster-dev-2 # Hostname/IP of the first data node
NodeId=2 # Node ID for this data node
datadir=/var/lib/mysql-cluster/data # Remote directory for the data files

[ndbd]
hostname=wocu-ha-mysqlcluster-dev-3 # Hostname/IP of the second data node
NodeId=3 # Node ID for this data node
datadir=/var/lib/mysql-cluster/data # Remote directory for the data files

[mysqld]
# SQL node options:
hostname=wocu-ha-mysqlcluster-dev-4

Thanks