MySQL Bugs: #24013: ndb_mgm -e "start backup wait completed" is not blocking for backup completion

Bug #24013	ndb_mgm -e "start backup wait completed" is not blocking for backup completion
Submitted:	6 Nov 2006 14:48	Modified:	22 Nov 2006 15:23
Reporter:	Jim Dowling	Email Updates:
Status:	Can't repeat	Impact on me:	None
Category:	MySQL Cluster: Cluster (NDB) storage engine	Severity:	S2 (Serious)
Version:	5.1.12	OS:	Linux (Linux)
Assigned to:	Geert Vanderkelen	CPU Architecture:	Any
Tags:	NDB_MGM, start backup

Description:
>ndb_mgm -e "start backup wait completed" 
does not block waiting for backup completion or return the backup-id.

In previous versions of 5.1 (5.1.11-beta), passing "start backup" as a command to be executed by ndb_mgm, caused the the ndb_mgm client to block until the backup completed.

We have a 2-node, 2-mgmd configuration.

How to repeat:
ndb_mgm -c "nodeid=60;localhost:23131,localhost:23132" -e "START BACKUP WAIT COMPLETED"
Connected to Management Server at: localhost:23131
Waiting for completed, this may take several minutes

config.ini

[NDBD DEFAULT]
NoOfReplicas=2
DataMemory=80M  # Reduced to total 100M per replica
IndexMemory=20M
NoOfFragmentLogFiles=25
TimeBetweenLocalCheckpoints=6
MaxNoOfConcurrentOperations=12500
TransactionInactiveTimeout=30000        # 30seconds of inactivity=rollback

[NDB_MGMD]
Hostname=localhost
nodeid=62
portnumber=23131
DataDir=/var/lib/mysql-cluster/dbmgmd1

[NDB_MGMD]
Hostname=localhost
nodeid=63
portnumber=23132
DataDir=/var/lib/mysql-cluster/dbmgmd2

[NDBD]
HostName=localhost
datadir=/var/lib/mysql-cluster/dbdata1
nodeid=1

[NDBD]
HostName=localhost
datadir=/var/lib/mysql-cluster/dbdata2
nodeid=2

# Auto-enumerated API node slots,
# Counting down from 61
#
[MYSQLD]
nodeid=61
[MYSQLD]
nodeid=60
[MYSQLD]
nodeid=59
[MYSQLD]
nodeid=58
[MYSQLD]
nodeid=57
[MYSQLD]
nodeid=56
[MYSQLD]
nodeid=55
[MYSQLD]
nodeid=54
[MYSQLD]
nodeid=53
[MYSQLD]
nodeid=52
[MYSQLD]
nodeid=51
[MYSQLD]
nodeid=50
[MYSQLD]
nodeid=49
[MYSQLD]
nodeid=48
[MYSQLD]
nodeid=47
[MYSQLD]
nodeid=46

Upgrading it to serious for us, as our sleep workaround is not considered acceptable.

I could not repeat this with 5.1.12 or latest from the repository.

 shell> ndb_mgm -e "START BACKUP WAIT COMPLETED"

This waits for the backup to finish, even without the WAIT COMPLETED option.
One needs lots of data in memory to see the process actually wait. With 80Mb of data memory the backups might be ready to fast (which is good of course), but it might look like it doesn't wait.