Bug #19162 Backup can't start if sum of BackupDataBufferSize/BackupLogBufferSize gt 4M

• Submitted: 18 Apr 2006 11:32
• Modified: 5 Aug 2006 14:02
• Reporter: Serge Kozlov
• Status: Closed
• Category: MySQL Server: Documentation
• Severity: S3 (Non-critical)
• Version: 4.1 ->
• OS: Linux (Linux FC4)
• Assigned to: Jon Stephens
• CPU Architecture: Any

[18 Apr 2006 11:32] Serge Kozlov

Description:
Backup cannot start if following conditions are true:
1. Variable BackupMemory isn't defined in config.ini (seems cluster try to use default value - 4M)
2. BackupDataBufferSize/BackupLogBufferSize variables added to configuration and their sum greater that 4M.
In this case 'START BACKUP' command returns the error:

ndb_mgm> start backup
Connected to Management Server at: localhost:1186
Waiting for completed, this may take several minutes
Node 2: Backup 1 started from 1 has been aborted. Error: 1342
Node 3: Backup 1 started from 1 has been aborted. Error: 1342
Start of backup failed
*  3001: Could not start backup
*        Backup failed to allocate buffers (check configuration): Permanent erro
r: Application error

How to repeat:
1. Add to config.ini following variables:
BackupDataBufferSize: 3M 
BackupLogBufferSize: 2M
2. Don not define BackupMemory!
3. Run the cluster.
4. Start backup through 'START BACKUP' command.
5. See error message in Description.

Suggested fix:

[4 Aug 2006 9:23] Jonas Oreland

Currently it's a fact that BackupMemory must be sum of 
  BackupDataBufferSize and BackupLogBufferSize

This might change...

[5 Aug 2006 14:02] Jon Stephens

Updated BackupMemory parameter info, added note to Cluster Backup Troubleshooting section of Cluster chapter.