I have a cluster running with 4 datanodes and when inserting data into a table with several million rows I encounter the following problem:
Status: Temporary error, restart node
Message: Internal program error (failed ndbrequire) (Internal error, programming error or missing error message, please report a bug)
Error: 2341
Error data: Dbdict.cpp
Error object: DBDICT (Line: 28216) 0x00000002
Program: ndbd
Pid: 11672
Version: mysql-5.5.19 ndb-7.2.4
Trace: /usr/local/mysql/my_cluster/ndb_data/ndb_3_trace.log.1 [t1..t1]
I tried to restart the node, but it is stuck in the start phase and pretends to be nodegroup 0 (it should be 1).
This seems to be a bug. How can I avoid it?
How can I restore data from datanode004 to datanode003?
This is my config.ini:
[ndb_mgmd]
hostname=mysqlnode001
datadir=c:\mysql\my_cluster\ndb_data
NodeId=50
[ndbd default]
noofreplicas=2
datadir=c:\mysql\my_cluster\ndb_data
datamemory=25000M
indexmemory=5000M
serverport=1186
### Params for REDO LOG
InitFragmentLogFiles=SPARSE
NoOfFragmentLogFiles=50
RedoBuffer=64M
### Params for LCP
DiskCheckpointSpeedInRestart=100M
DiskCheckpointSpeed=10M
TimeBetweenLocalCheckpoints=20
TotalSendBufferMemory=100M
[ndbd]
hostname=datanode001
NodeId=1
datadir=/usr/local/mysql/my_cluster/ndb_data
[ndbd]
hostname=datanode002
NodeId=2
datadir=/usr/local/mysql/my_cluster/ndb_data
[ndbd]
hostname=datanode003
NodeId=3
datadir=/usr/local/mysql/my_cluster/ndb_data
[ndbd]
hostname=datanode004
NodeId=4
datadir=/usr/local/mysql/my_cluster/ndb_data
[mysqld]
NodeId=51
[mysqld]
NodeId=52
[mysqld]
NodeId=53
[mysqld]
NodeId=54
Status: Temporary error, restart node
Message: Internal program error (failed ndbrequire) (Internal error, programming error or missing error message, please report a bug)
Error: 2341
Error data: Dbdict.cpp
Error object: DBDICT (Line: 28216) 0x00000002
Program: ndbd
Pid: 11672
Version: mysql-5.5.19 ndb-7.2.4
Trace: /usr/local/mysql/my_cluster/ndb_data/ndb_3_trace.log.1 [t1..t1]
I tried to restart the node, but it is stuck in the start phase and pretends to be nodegroup 0 (it should be 1).
This seems to be a bug. How can I avoid it?
How can I restore data from datanode004 to datanode003?
This is my config.ini:
[ndb_mgmd]
hostname=mysqlnode001
datadir=c:\mysql\my_cluster\ndb_data
NodeId=50
[ndbd default]
noofreplicas=2
datadir=c:\mysql\my_cluster\ndb_data
datamemory=25000M
indexmemory=5000M
serverport=1186
### Params for REDO LOG
InitFragmentLogFiles=SPARSE
NoOfFragmentLogFiles=50
RedoBuffer=64M
### Params for LCP
DiskCheckpointSpeedInRestart=100M
DiskCheckpointSpeed=10M
TimeBetweenLocalCheckpoints=20
TotalSendBufferMemory=100M
[ndbd]
hostname=datanode001
NodeId=1
datadir=/usr/local/mysql/my_cluster/ndb_data
[ndbd]
hostname=datanode002
NodeId=2
datadir=/usr/local/mysql/my_cluster/ndb_data
[ndbd]
hostname=datanode003
NodeId=3
datadir=/usr/local/mysql/my_cluster/ndb_data
[ndbd]
hostname=datanode004
NodeId=4
datadir=/usr/local/mysql/my_cluster/ndb_data
[mysqld]
NodeId=51
[mysqld]
NodeId=52
[mysqld]
NodeId=53
[mysqld]
NodeId=54