[MySQL-cluster] Backup error

Hi,

Getting this from a quad non-replicated node set-up, mgmd is on another box

Connected to Management Server at: 172.23.77.231:1186
Waiting for completed, this may take several minutes
Node 2: Backup request from 1 failed to start. Error: 1302
Start of backup failed
* 3001: Could not start backup
* Out of backup record: Permanent error: Internal error

Can't see anything on the mailing list.

Config is.

[NDBD DEFAULT]
NoOfReplicas=1

DataMemory=1600Mb
IndexMemory=200Mb

MaxNoOfAttributes=2000

MaxNoOfTables=256
MaxNoOfUniqueHashIndexes=256
MaxNoOfOrderedIndexes=256

FileSystemPath=/mysqlcluster
BackupDataDir=/mysqlbackup

MaxNoOfConcurrentOperations=500000

TransactionDeadlockDetectionTimeout=2400

[MYSQLD DEFAULT]
[NDB_MGMD DEFAULT]
[TCP DEFAULT]

SendBufferMemory=512KB

# Managment Server
[NDB_MGMD]
Id=1
HostName=172.23.77.231
DataDir=/usr/local/mysql/cluster

# Storage Engines
[NDBD]
Id=2
HostName=172.23.77.232
DataDir=/usr/local/mysql/cluster

[NDBD]
Id=3
HostName=172.23.77.232
DataDir=/usr/local/mysql/cluster

[NDBD]
Id=4
HostName=172.23.77.232
DataDir=/usr/local/mysql/cluster

[NDBD]
Id=5
HostName=172.23.77.232
DataDir=/usr/local/mysql/cluster

[MYSQLD]
[MYSQLD]

Show Output

Connected to Management Server at: 172.23.77.231:1186
Cluster Configuration
---------------------
[ndbd(NDB)] 4 node(s)
id=2 @172.23.77.232 (Version: 4.1.11, Nodegroup: 0, Master)
id=3 @172.23.77.232 (Version: 4.1.11, Nodegroup: 1)
id=4 @172.23.77.232 (Version: 4.1.11, Nodegroup: 2)
id=5 @172.23.77.232 (Version: 4.1.11, Nodegroup: 3)

[ndb_mgmd(MGM)] 1 node(s)
id=1 @172.23.77.231 (Version: 4.1.11)

[mysqld(API)] 2 node(s)
id=6 @172.23.77.232 (Version: 4.1.11)
id=7 (not connected, accepting connect from any host)



Stewart Burnett | Capgemini | Sale
Lead Solutions Designer | ATOC Software Architect
Tel. +44 (0) 870 906 7013 | Int. 700 7013 | www.capgemini.com
Join the Collaborative Business Experience



This message contains information that may be privileged or confidential and is the property of the Capgemini Group. It is intended only for the person to whom it is addressed. If you are not the intended recipient, you are not authorized to read, print, retain, copy, disseminate, distribute, or use this message or any part thereof. If you receive this message in error, please notify the sender immediately and delete all copies of this message.

Hi,
Looks very much like an internal memory leak bug, please report it as a
bug. The problem should go away
if you perform a "rolling upgrade" of the cluster since node restarts
will return all lists to a proper state.

Rgrds Mikael

2005-07-27 kl. 10.59 skrev Burnett, Stewart:
Mikael Ronstrom, Senior Software Architect
MySQL AB, www.mysql.com

Jumpstart your cluster:
http://www.mysql.com/consulting/packaged/cluster.html