Bug #9960 START BACKUP reports failure albeit succeding
Submitted: 17 Apr 2005 17:03 Modified: 25 Apr 2005 11:05
Reporter: Johan Andersson Email Updates:
Status: Closed Impact on me:
None 
Category:MySQL Cluster: Cluster (NDB) storage engine Severity:S2 (Serious)
Version:5.0.3 OS:Linux (linux 2.4.21-20 (64-bit))
Assigned to: Jonas Oreland CPU Architecture:Any

[17 Apr 2005 17:03] Johan Andersson 
Description:
started a backup of 50M rows.  After some time the ndb_mgm reports:
Error in mgm protocol parser. cmd: 'start backup' status=2, curr=
Start of backup failed
* 0:No error
*   Executing: ndb_mgm_disconnect

How to repeat:
populate a db with a lot of data.
start a backup. Go to lunch (that is what we did).
The backup was the only thing running on the cluster.

Suggested fix:
-
[22 Apr 2005 6:39] Jonas Oreland 
I increased wait for completion timeout to 48 hours...
However, start backup [NOWAIT | WAIT STARTED] is probably prefered
  for long running backups
[22 Apr 2005 7:08] Bugs System 
A patch for this bug has been committed. After review, it may
be pushed to the relevant source trees for release in the next
version. You can access the patch from:

  http://lists.mysql.com/internals/24215