Bug #19880 Backup fails if BackupLogBufferSize hasn't default value
Submitted: 17 May 2006 12:53 Modified: 7 Nov 2006 14:31
Reporter: Serge Kozlov Email Updates:
Status: Closed Impact on me:
None 
Category:MySQL Cluster: Cluster (NDB) storage engine Severity:S2 (Serious)
Version:5.1.10 (beta) OS:Linux (Linux FC4)
Assigned to: Stewart Smith CPU Architecture:Any

[17 May 2006 12:53] Serge Kozlov 
Description:
If BackupLogBufferSize has not default value in config.ini then cluster backup can't work properly and produces following error message:

Current byte-offset of file-pointer is: 568

Time: Wednesday 17 May 2006 - 14:43:51
Status: Temporary error, restart node
Message: Assertion (Internal error, programming error or missing error message,
please report a bug)
Error: 2301
Error data: ArrayPool<T>::getPtr
Error object: ../../../../../storage/ndb/src/kernel/vm/ArrayPool.hpp line: 425 (
block: BACKUP)
Program: /home/ndbdev/skozlov/builds/libexec/ndbd
Pid: 23245
Trace: /space/run/ndb_2_trace.log.1
Version: Version 5.1.10 (beta)
***EOM***

How to repeat:
1. Add BackupLogBufferSize=10M to config.ini in [ndbd default] section
2. Start a cluster.
3. Run ndb_mgm.
4. Start backup (START BACKUP command)
5. See error_log in description.
[18 May 2006 4:09] Tomas Ulin 
please provide config.ini and trace files
[18 May 2006 14:09] Serge Kozlov 
trace, log files and config.ini

Attachment: bug19880.tar.gz (application/gzip, text), 95.44 KiB.
[29 May 2006 5:48] Hartmut Holzgraefe 
Verified using latest 5.1bk,

in 5.1 this failes hard, in 5.0 the backup is refused with the following message:

  Node 2: Backup 1 started from 1 has been aborted. Error: 1342
  Node 3: Backup 1 started from 1 has been aborted. Error: 1342

when raising the BackupLogBufferSize parameter to 10M
[3 Nov 2006 5:41] Stewart Smith 
Fixed in current BK tree. Reports error due to bad configuration (as in 5.0). With appropriately configured BackupMemory, backup goes okay.
[7 Nov 2006 14:31] Serge Kozlov 
Correct error message for 5.1.13-bk.